Masko in Devin
Devin can create a mascot for the app it is building through Masko's MCP server. It creates the mascot, its poses and its animations, then puts the finished files in your repository. Your app plays those files and never calls Masko.
The connection lives in your Devin plugins, so it works in cloud sessions, Devin Desktop and the Devin CLI.
Connect Masko
Devin signs in to Masko, so nobody copies a key.
- In Devin, open Customize → MCPs, click + at the top right, then New MCP.
- Name it Masko, set Transport type to HTTP, Server URL to
https://masko.ai/api/mcpand Authentication to OAuth. - Click Add, tick I understand and want to proceed and click Add again.
- Masko's sign-in page opens. Choose the workspace whose credits Devin will use and click Connect Masko.
- Back in Devin, open masko, scroll to Test tools and click Test. Devin lists Masko's tools.
Generation spends the credits of the workspace you chose. Only a team owner or admin can connect a team workspace. To add Masko, your Devin role needs permission to manage MCP servers.
Try it
- "Show my Masko credit balance. Don't generate anything."
- "Add a friendly mascot to this app. It waits on the home screen and celebrates when a task is done. Tell me the cost before generating."
- "Export the mascot's idle and celebrate animations and play them with the Masko player."
What Devin can do
- Create a mascot, its poses and its animations.
- Check a job until its files are ready.
- 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 your key belongs to. Ask Devin for the estimated cost before generating: the estimate tools return it before anything is spent. Devin's own session usage is billed by Devin.
Playback
Play the files with the Masko player (npm install @masko/player). A single loop needs only its two hosted files: <MaskoPlayer clip={{ webm, hevc }} /> (one animation). A mascot that changes clips is a canvas release, which your app drives with set and fire. Ask Devin to export the release once with public links and commit that delivery with your app.
New mascots made through the MCP server start with public CDN hosting off. Publish the mascot's assets before using CDN links in a public app.
Limits
- The connection works while Devin builds. Your shipped app cannot reach Masko through it.
- The connection allows 120 requests per minute per key.
Security
- Devin keeps the sign-in Masko gave it and sends it with each request. No Masko key goes into Devin or your repository.
- Your app only plays files and needs no Masko key.
- To remove access, disconnect Devin in Connected apps and uninstall the server in Customize → MCPs.
