Masko in n8n
n8n reaches Masko through its MCP server. An AI Agent can use Masko's tools on its own, for example to create a mascot and animate it from a chat. A workflow can also call one Masko tool as a fixed step, such as reading your credits or checking a job.
Create the credential
On n8n Cloud, n8n signs in to Masko, so nobody copies a key. The credential is created once and every Masko node reuses it.
- In any Masko node below, set Authentication to MCP OAuth2, open the credential list and choose Create new credential.
- Set Server URL to
https://masko.ai/api/mcpand keep Use Dynamic Client Registration on. Name the credential Masko and click Save. - Click Connect. In the window that opens, choose the workspace whose credits n8n will use and click Connect Masko.
Generation spends the credits of the workspace you chose. Only a team owner or admin can connect a team workspace.
Self-hosted n8n
Self-hosted n8n connects with an API key instead:
- On masko.ai, open Developers → API keys, choose Create API key, name it n8n and keep Read + Write. Copy the key: it is shown once.
- In any Masko node below, set Authentication to Bearer Auth, open the credential list and choose Create new credential.
- Paste the key into Bearer Token, without the word Bearer: n8n adds it. Name the credential Masko and click Save.
The key belongs to the workspace you were in when you created it, personal or team. Only a team owner or admin can create a team key.
Give an AI Agent Masko's tools
- In the AI Agent node, click + under Tool and choose MCP Client Tool.
- Set Endpoint to
https://masko.ai/api/mcpand keep Server Transport on HTTP Streamable. - Set Authentication to MCP OAuth2, or Bearer Auth on self-hosted n8n, and pick the Masko credential.
- Set Tools to Include to Selected and pick the tools the agent needs. A short list keeps the agent on task and leaves out paid tools you did not plan for.
Try it in the chat:
- "Show my Masko credit balance. Don't generate anything."
- "Create a fox mascot for my newsletter and tell me the cost before animating it."
Call one tool as a step
Use the MCP Client node when the workflow should always do the same thing.
- Add an MCP Client node after your trigger.
- Keep Server Transport on HTTP Streamable and set MCP Endpoint URL to
https://masko.ai/api/mcp. - Set Authentication to MCP OAuth2, or Bearer Auth on self-hosted n8n, and pick the Masko credential.
- Choose the Tool, for example
get_credits, and fill its inputs. - Click Execute step.
The node returns the tool's result in content[0].text. For get_credits, that holds data.total with your balance.
Wait for a generation
Generation tools answer at once with a job, and the files arrive later. Continue the workflow in one of two ways:
- Check the job. Add a Wait node, then an MCP Client node with
get_joband the job's ID. Loop until the status iscompletedorfailed. A wait of 30 seconds or more between checks is plenty. - Get called back. Add a Webhook trigger in a second workflow and register its production URL as a Masko webhook for
job.completedandjob.failed. Masko posts the job with its file links when it finishes. Check the signature before trusting the payload.
What the tools do
- Create a mascot, its poses and its animations.
- Make talking animations and backgrounds.
- Build a canvas, the mascot's states and the moments that switch between them.
- Export and publish assets, and get their CDN links.
- Read your credit balance and open a credit checkout link.
Costs
Generation uses credits from the Masko workspace you connected. The estimate tools return the cost before anything is spent: put one before any paid tool in a workflow that runs on its own. Reading, listing and checking jobs are free.
Limits
- The connection allows 120 requests per minute. Space out loops that check jobs.
- New mascots made through the MCP server start with public CDN hosting off. Publish the mascot's assets before sending CDN links anywhere public.
Security
- n8n keeps its Masko sign-in, or your key, in the credential and sends it with each request to Masko. With a key, create one just for n8n, so you can revoke it on its own.
- To remove access, delete the credential in n8n, then disconnect n8n in Connected apps or revoke its key in Developers → API keys.
