Anima MCP

claude mcp add --transport http anima https://public-api.animaapp.com/v1/mcp

📘
Connect your AI coding agent to Anima Playground, Figma designs, and your team's design system.

Anima MCP gives MCP-compatible agents direct, authenticated access to Anima. Your agent can move between designs, code, and live playgrounds without manual exports or copy-paste.

What you can do with Anima MCP

Build new playgrounds

Start from a prompt, a public website, a Figma design, an empty repository, or an existing local codebase. Anima can generate a new app, import your files, and return a shareable playground URL.

Generated playgrounds run asynchronously. Your agent can wait for generation to finish and report the completed result instead of leaving you with an in-progress job.

Continue working on existing playgrounds

Anima playgrounds are real Git repositories. An agent can list the team's playgrounds, get short-lived repository access, clone a project, edit it locally, and push changes back to the live playground.

The MCP can also update a playground's name or visibility without changing its code.

Turn Figma designs into production-ready code

Give your agent a Figma URL and ask it to implement the selected frames in your project. Anima generates code and assets for your stack, plus visual snapshots and implementation guidance that help the agent match the original design accurately.

Use your team's design system

Agents can read your Anima design-system documentation and retrieve the relevant component, token, and implementation guidance before building. This helps generated work follow your team's established visual language and code patterns.

Design-system access may require an Enterprise setup. Contact us to get it configured.

Share or publish

Every playground has a shareable Anima URL. When you explicitly ask to deploy publicly, your agent can publish the playground to a live URL, and it can take that deployment offline again later without deleting the playground.

🔗
Sharing a playground URL and publishing a public site are different actions. Publishing makes the deployed site public to the world.

Setup

Requirements

MCP-compatible AI coding tool: Claude Code, Cursor, or another client that supports remote HTTP MCP servers
Anima account: Sign in to access your team's playgrounds and approved capabilities
Figma access (optional): Connect Figma when you want to generate code from Figma designs

Claude Code

Run this command in your terminal:

claude mcp add --transport http anima https://public-api.animaapp.com/v1/mcp

Then:

Restart Claude Code.
Enter /mcp to open the MCP menu.
Select Anima and authenticate in the browser.
Optionally connect your Figma account to enable Figma flows.

Cursor

Open the Command Palette (⌘ + Shift + P on macOS, Ctrl + Shift + P on Windows).
Open Cursor Settings > Tools & MCP.
Click Add Custom MCP.
Add this configuration to mcp.json:

{
  "mcpServers": {
    "anima": {
      "url": "https://public-api.animaapp.com/v1/mcp"
    }
  }
}

Find Anima under Installed MCP Servers and click Connect.
Authenticate with your Anima account in the browser.
Optionally connect your Figma account to enable Figma flows.

Other MCP clients

Use this remote HTTP endpoint:

https://public-api.animaapp.com/v1/mcp

Your client must support OAuth for browser-based authentication, or a Bearer token for an approved headless setup.

MCP or Anima CLI?

Use Anima MCP when you want native Anima tools available inside an MCP-compatible client.

Use the Anima CLI when an agent needs to connect and start working from a terminal in the current session. The CLI can log in with a human-approved device flow, list playgrounds, import code, get Git access, and publish when asked. It can also generate MCP configuration for future sessions.

Troubleshooting

Can't access a playground

Make sure your Anima account or agent identity has access to that playground. Private playgrounds require the right team membership or sharing permissions.

MCP asks for authentication

This is expected. Complete the browser sign-in and approve the requested workspace access. Headless agents need an approved Bearer token.

MCP tools do not appear

Verify the endpoint, finish authentication, and restart or reload your MCP client. Many clients discover tools only when a session starts.

Figma generation is unavailable

Connect Figma during authentication and make sure your account can access the referenced Figma file.