Anima MCP Server

io.github.AnimaAppPublished by GitHub account AnimaAppv1.0.0Updated Oct 24, 2026

Connect AI coding agents to Anima Playground, Figma, and your design system.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsMedia & Design

Overview

AI-generated overview

Anima's Agent Grid MCP server lets a coding agent build, host, edit and publish web apps as git-backed artifacts, including from Figma designs.

What you can do
Build apps from a prompt, a website URL or Figma frames, returning a live preview URL and optionally parallel variants for comparison. Host existing code by importing a project or starting an empty repo and pushing to it. Edit artifacts over git: clone, commit and push changes to a team workspace repository. Publish an app to a public URL or take it down again. Generate design-aware code into your own codebase from Figma frames, matched to your stack.
When to use it
Useful when you want a coding agent to turn a description, an existing site or a Figma design into a running web app, to iterate on hosted artifacts through git, or to implement Figma designs directly in your own repository.
Requirements
A remote streamable HTTP endpoint; an Agent Grid account; OAuth authentication in the browser when prompted; an MCP-capable client such as Claude Code, Codex, Cursor or VS Code (VS Code requires GitHub Copilot). Connecting Figma during authentication is optional and needed for Figma flows. Design system access is Enterprise-only and set up with the team.
Before you install
Publishing makes an app public to the world, so confirm intent before publishing. The agent writes to git repositories in your team workspace (clone, commit, push) and can import and modify code. Authentication is OAuth through a browser and may grant access to connected Figma content; git token expiry is a known issue. Design system features require an Enterprise arrangement.

Installation

In SourceWeft

  1. Open Anima MCP Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.AnimaApp%2Fanima/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Agent Grid MCP Server Guide

Agent Grid is a governed hub, by Anima, where AI agents build, host, publish, and share web apps. This repo is the MCP server guide and the skill that teaches your coding agent to use it — install it as a Claude Code plugin, a Codex skill, or a plain MCP server.

Agent Grid lives at app.agentgrid.io. For the full docs, see our help documentation.

What your agent can do

  • Build an app from a prompt, a website, or a Figma design — describe it, clone a URL, or hand over Figma frames, and get back a running app at a live URL.
  • Host code you already have — import a project or start an empty repo, and push to it.
  • Edit any artifact over git — every artifact is a real git repository; clone, commit, push.
  • Publish to a live public URL — and take it down again.
  • Generate design-aware code into your own codebase — Figma frames to files in your repo, matched to your stack.

Everything is an artifact: one git repo in your team's workspace, addressed by its sessionId.

Quick start: Claude Code plugin

/plugin marketplace add AnimaApp/mcp-server-guide/plugin install anima@mcp-server-guide

This configures the MCP server and installs the skill. Authenticate when prompted. That's it.

Installation & setup

Requirements

  • An MCP-capable AI coding tool — Claude Code, Codex, Cursor, VS Code, or anything speaking streamable HTTP
  • An Agent Grid account

Server URL: https://api.agentgrid.io/v1/mcp · Transport: streamable HTTP

Claude Code (manual)

  1. In your terminal (not inside Claude Code):
bash
claude mcp add --transport http anima https://api.agentgrid.io/v1/mcp
  1. Restart Claude Code
  2. Run /mcp, select anima, and authenticate in the browser
  3. (Optional) Connect Figma during authentication to enable the Figma flows

Manage servers with claude mcp list, claude mcp get anima, claude mcp remove anima. See Anthropic's MCP documentation.

OpenAI Codex

bash
codex mcp add anima --url https://api.agentgrid.io/v1/mcp

Or in ~/.codex/config.toml:

toml
[mcp_servers.anima]url = "https://api.agentgrid.io/v1/mcp"

Then install the skill (recommended):

bash
codex skill install AnimaApp/mcp-server-guide/skills/anima

See OpenAI's Codex MCP documentation.

VS Code

  1. Cmd Shift P / Ctrl Shift P → MCP: Add Server
  2. Select HTTP
  3. URL: https://api.agentgrid.io/v1/mcp
  4. Server ID: anima
  5. Choose global or workspace scope
json
{  "servers": {    "anima": {      "type": "http",      "url": "https://api.agentgrid.io/v1/mcp"    }  }}

[!NOTE] MCP in VS Code requires GitHub Copilot. See VS Code's documentation.

Cursor

Cursor > Settings > Cursor Settings > MCP > + Add new global MCP server:

json
{  "mcpServers": {    "anima": {      "url": "https://api.agentgrid.io/v1/mcp"    }  }}

Click Connect to authenticate. See Cursor's documentation.

Any other client

json
{  "mcpServers": {    "anima": {      "url": "https://api.agentgrid.io/v1/mcp"    }  }}

No MCP? Use the CLI

The Anima CLI runs the same tools from a shell — no MCP server to configure:

bash
npx @animaapp/cli@latest loginnpx @animaapp/cli@latest create -t p2c -p "SaaS dashboard with sidebar and analytics"

Prompting your agent

Build something new

"Build me a SaaS analytics dashboard with a sidebar, KPI cards, and an activity feed."

Your agent creates an artifact, waits for the build, and hands back a live preview URL. Ask for variants and it can generate several in parallel to compare.

Clone a site or implement a Figma design as a live app

"Clone stripe.com/payments into an app." "Turn this Figma frame into a working site: https://figma.com/design/..."

Edit an existing artifact

"The header on https://app.agentgrid.io/artifacts/xyz is broken on mobile — fix it."

The agent clones the artifact's git repo, fixes it, and pushes. Content changes always go through git.

Implement a Figma design in your own codebase

"Implement this Figma design in my project: https://figma.com/design/..."

The agent generates code matched to your stack and uses the returned design snapshots as visual reference.

Publish

"Publish it."

Publishing makes an app public to the world — it isn't needed just to share, since the artifact URL is already viewable.

Design system access (Enterprise)

"Implement a login form following our design system, using this Figma URL: ..."

Design system setup is done with our team. Contact us to get it configured.

Best practices

Describe intent, not CSS. Agent Grid is design-aware; hex values and pixel dimensions in a prompt override that and produce generic results. Say what it's for, who it's for, and the 3–5 features that matter.

Be specific when implementing. "Implement the login form using our existing Button and Input components from src/components/ui" beats "implement this design".

Break down large designs. Header first, then the card grid, then the footer. Focused requests are more accurate.

Troubleshooting

Common issues — async generation, create-type validation, git token expiry, publish semantics — are covered in the skill's troubleshooting reference.

MCP not recognized: confirm the server is configured in your tool and that authentication completed. Authentication issues: remove and re-add the server, clear cookies, restart your client.

What's in this repo

PathPurpose
skills/anima/SKILL.mdThe skill your agent reads
skills/anima/references/Tool reference, setup, git workflow, examples, troubleshooting
.claude-plugin/Claude Code plugin and marketplace manifests
.mcp.jsonMCP server the plugin installs
server.jsonMCP Registry entry
anima/SKILL.mdMirror of the skill, kept in sync by CI

Additional resources

Source: README.md at commit 45bf229

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.