Masko for Muse
Connect Masko to Muse to create mascots, animate your own artwork and use the assets in your app or website. Masko accepts Muse sign-ins; the connector appears in Muse once Meta finishes its review.
Workflows
| Workflow | Example prompt |
|---|---|
| Create a mascot from an idea or an existing character | "Create a friendly mascot for my fitness app." |
| Generate consistent poses and animate an uploaded character | "Animate my uploaded mascot waving hello with a transparent background." |
| Build a canvas with idle loops, reactions and transitions | "Make my mascot celebrate when someone completes a lesson, then return to idle." |
| Add completed assets to a website or app with the Masko player | "Show me how to add my animations to React without flickering." |
| Find projects and mascots, check credits and follow jobs | "Show my mascots and credit balance. Do not generate anything." |
Account access and credits
When you connect, Masko asks you to sign in, choose one personal or team workspace and approve what Muse can do. The connection uses that workspace's permissions and its own credit balance. Review the cost before generating, and check a pending job instead of starting another paid generation. Disconnect Muse at any time under Connected apps.
Credits are bought on Masko's billing page through Stripe, not inside Muse. No tool takes a payment: the agent points you to Billing when credits run short (credits and costs).
Assets and integration
New mascots start private, and public hosting needs an explicit request. Private preview links stop working within hours, so a single animation in production plays from the permanent public links that publishing gives. An app reads an interactive mascot's canvas with an app key, which can only read that mascot's released canvases.
Interactive mascots play with the Masko player, which runs the canvas; your app sends its events to canvas inputs with set and fire. Single clips play in the Masko player from their hosted files (play one animation). The connector does not deploy your app or activate Masko for Mac.
Technical details for integration review
| Setting | Value |
|---|---|
| Hosted MCP endpoint | https://masko.ai/api/mcp |
| Transport | Streamable HTTP |
| Authentication protocol | OAuth with PKCE, no client secret |
| OAuth client ID | https://masko.ai/oauth/clients/muse |
| Callback URLs | https://muse.ai/api/hatch/oauth/callback, https://platform.muse.ai/oauth/credential-test/callback |
| Authorization scopes | masko:read, masko:write |
| Muse connection status | Live on Masko; in Meta's connector review |
The server exposes tools for mascots, poses, animations, backgrounds, voices and talking, jobs, exports and public links, canvases and app keys, the docs and feedback to the Masko team. Masko accepts the Muse client only with its two callback URLs; a read-only connection lists only the tools that change nothing. A host that sends an Authorization: Bearer header can connect with a Masko API key instead; see MCP server. See Masko in ChatGPT for the existing integration and muse.ai/platform for Muse's connector program.
Support
Contact paul@masko.ai for integration or reviewer access. Never send passwords, API keys, authorization codes or connection tokens.
