Anima MCP Server
Server Details
Connect AI coding agents to Anima Playground, Figma, and your design system.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AnimaApp/mcp-server-guide
- GitHub Stars
- 6
- Server Listing
- Anima MCP Server
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
playground-create1 field changed- changed
Input schema / properties / name / descriptionPrevious value: -"empty and import only. Defaults to \"Untitled project\". Rename existing playgrounds via playground-metadata-update."New value: +"Display name; applied by empty and import only (default \"Untitled project\"). p2c, l2c and f2c name the playground from the generated content and IGNORE this. Rename any playground afterwards via playground-metadata-update."
1 tool update
- Added
playground-status
2 tool updates
- Changed
playground-create14 fields changed- changed
Input schema / properties / fileKey / descriptionPrevious value: -"[f2c only] Figma file key. Required when type is f2c."New value: +"REQUIRED for f2c only. Figma file key of the design; f2c also requires the X-Figma-Token header." - added
Input schema / properties / filesAdded value: +{ + "additionalProperties": { + "type": "string" + }, + "description": "import only, inline transport: path-to-UTF-8-text map, becomes the first commit. TEXT only, up to roughly 100 KB of source; binaries or larger use zipUploadId via playground-get_zip_upload_url. Mutually exclusive with zipUploadId.", + "propertyNames": { + "maxLength": 512, + "type": "string" + }, + "type": "object" +} - changed
Input schema / properties / framework / descriptionPrevious value: -"Target framework — ONLY html and react are supported; Anima does not generate or host other frameworks (no vue, svelte, angular, etc.). REQUIRED for blank — declare what you are about to push. Optional for generation types (p2c/l2c/f2c), defaulting to html."New value: +"ONLY html and react exist. REQUIRED for empty (declare react if pushing React code). Optional for import (auto-detected from package.json) and for p2c/l2c/f2c (defaults to html)." - changed
Input schema / properties / guidelines / descriptionPrevious value: -"[p2c only] Additional coding guidelines for the generation."New value: +"Optional, p2c only. Guidelines to steer generation (conventions, structure, libraries)." - changed
Input schema / properties / language / descriptionPrevious value: -"Programming language (react framework only). f2c: typescript or javascript. l2c: always typescript. Not used for p2c or html framework."New value: +"typescript or javascript; generation types with framework react only, ignored otherwise. l2c output is always typescript." - changed
Input schema / properties / name / descriptionPrevious value: -"[blank only] Project name shown in Anima. Defaults to \"Untitled project\"."New value: +"empty and import only. Defaults to \"Untitled project\". Rename existing playgrounds via playground-metadata-update." - changed
Input schema / properties / nodesId / descriptionPrevious value: -"[f2c only] Figma node IDs to convert. Required when type is f2c."New value: +"REQUIRED for f2c only. Figma node IDs of the frames to convert." - changed
Input schema / properties / prompt / descriptionPrevious value: -"[p2c only] Text prompt describing the UI to generate. Required when type is p2c."New value: +"REQUIRED for p2c only. Text prompt describing the UI to generate." - changed
Input schema / properties / styling / descriptionPrevious value: -"CSS styling. Valid values per type — p2c: tailwind, css, inline_styles. l2c: tailwind, inline_styles, vanilla_css. f2c: tailwind, plain_css, css_modules, inline_styles."New value: +"CSS strategy; generation types only, not empty or import. p2c: tailwind, css, inline_styles. l2c: tailwind, inline_styles, vanilla_css. f2c: tailwind, plain_css, css_modules, inline_styles." - changed
Input schema / properties / type / descriptionPrevious value: -"Generation type: p2c (prompt), l2c (website URL), f2c (Figma), blank (an EMPTY playground for code you wrote yourself — pair with project-get_git_token to push it)"New value: +"Where the code comes from. Anima GENERATES: p2c = text prompt (requires prompt); l2c = website URL (requires url); f2c = Figma frames (requires fileKey + nodesId + X-Figma-Token header). YOU supply: empty = empty git repo you push to (requires framework); import = your code as the first commit (EXACTLY ONE of files or zipUploadId)." - changed
Input schema / properties / type / enumPrevious value: -[ - "p2c", - "l2c", - "f2c", - "blank" -]New value: +[ + "p2c", + "l2c", + "f2c", + "empty", + "import" +] - changed
Input schema / properties / uiLibrary / descriptionPrevious value: -"UI component library (optional, react framework only). l2c: only shadcn is supported. f2c: mui, antd, shadcn, or clean_react. Not used for p2c."New value: +"Optional UI library; generation types with framework react only. l2c: shadcn only. f2c: mui, antd, shadcn, clean_react. Not for p2c." - changed
Input schema / properties / url / descriptionPrevious value: -"[l2c only] Website URL to convert to code. Required when type is l2c."New value: +"REQUIRED for l2c only. Website URL to convert to code." - added
Input schema / properties / zipUploadIdAdded value: +{ + "description": "import only: id from playground-get_zip_upload_url, used AFTER HTTP PUTting the zip to its uploadUrl; for binaries or over roughly 100 KB of source. Single-use; valid within 30 minutes of the last upload. Mutually exclusive with files.", + "format": "uuid", + "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", + "type": "string" +}
- Added
playground-get_zip_upload_url
1 tool update
- Added
playground-unpublish
1 tool update
- Added
playground-metadata-update
1 tool update
- Changed
playground-create2 fields changed- removed
Input schema / properties / framework / defaultRemoved value: -"react" - changed
Input schema / properties / framework / descriptionPrevious value: -"Target framework. Supported by all types."New value: +"Target framework — ONLY html and react are supported; Anima does not generate or host other frameworks (no vue, svelte, angular, etc.). REQUIRED for blank — declare what you are about to push. Optional for generation types (p2c/l2c/f2c), defaulting to html."
2 tool updates
- Changed
playground-create3 fields changed- added
Input schema / properties / nameAdded value: +{ + "description": "[blank only] Project name shown in Anima. Defaults to \"Untitled project\".", + "maxLength": 120, + "type": "string" +} - changed
Input schema / properties / type / descriptionPrevious value: -"Generation type: p2c (prompt), l2c (website URL), f2c (Figma)"New value: +"Generation type: p2c (prompt), l2c (website URL), f2c (Figma), blank (an EMPTY playground for code you wrote yourself — pair with project-get_git_token to push it)" - changed
Input schema / properties / type / enumPrevious value: -[ - "p2c", - "l2c", - "f2c" -]New value: +[ + "p2c", + "l2c", + "f2c", + "blank" +]
- Changed
project-get_git_token5 fields changed- added
Input schema / properties / sessionIdAdded value: +{ + "description": "The playground session id — the last path segment of the playground URL (e.g. \"mr25vsjppVtbMx\" from https://dev.animaapp.com/chat/mr25vsjppVtbMx), or the id from playground-create.", + "type": "string" +} - removed
Input schema / properties / session_idRemoved value: -{ - "description": "The playground session id — the last path segment of the playground URL (e.g. \"mr25vsjppVtbMx\" from https://dev.animaapp.com/chat/mr25vsjppVtbMx), or the id from playground-create.", - "type": "string" -} - added
Input schema / properties / ttlSecondsAdded value: +{ + "description": "Optional token lifetime in seconds. Default and maximum 3600 (1 hour); minimum 300. Expired tokens cannot be renewed — mint a new one and update the git remote.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" +} - removed
Input schema / properties / ttl_secondsRemoved value: -{ - "description": "Optional token lifetime in seconds. Default and maximum 3600 (1 hour); minimum 300. Expired tokens cannot be renewed — mint a new one and update the git remote.", - "maximum": 9007199254740991, - "minimum": -9007199254740991, - "type": "integer" -} - changed
Input schema / requiredPrevious value: -[ - "session_id" -]New value: +[ + "sessionId" +]
2 tool updates
- Removed
project-download_from_playground - Added
project-get_git_token
1 tool update
- Changed
playground-create2 fields changed- changed
Input schema / properties / styling / descriptionPrevious value: -"CSS styling. Valid values per type — p2c: tailwind, css, inline_styles. l2c: tailwind, inline_styles. f2c: tailwind, plain_css, css_modules, inline_styles."New value: +"CSS styling. Valid values per type — p2c: tailwind, css, inline_styles. l2c: tailwind, inline_styles, vanilla_css. f2c: tailwind, plain_css, css_modules, inline_styles." - changed
Input schema / properties / styling / enumPrevious value: -[ - "tailwind", - "css", - "inline_styles", - "plain_css", - "css_modules" -]New value: +[ + "tailwind", + "css", + "inline_styles", + "vanilla_css", + "plain_css", + "css_modules" +]
2 tool updates
- Added
design_system-get_files - Added
design_system-get_manifest
4 tool updates
- First observed
codegen-figma_to_code - First observed
playground-create - First observed
playground-publish - First observed
project-download_from_playground
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
- mcp-serverOAuthcom.make
Give your AI agents the tools to build, manage, and run automation workflows.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects Figma designs to AI agents, enabling extraction of production-ready code, assets, and design tokens through natural language descriptions. Supports React, Vue, CSS, and Tailwind with real-time design system analysis.81,58640MIT
- FlicenseNot gradedqualityDmaintenanceConnects an AI agent to Figma and Panda CSS for two-way design system sync, component creation, and variable binding.-
- AlicenseNot gradedqualityDmaintenanceConnects Figma designs to React components using your actual component library, enabling AI tools to generate production-ready code with proper imports.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.15630MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Most tools have distinct purposes, but codegen-figma_to_code and playground-create's f2c mode both convert Figma to code, creating potential confusion. The design system tools are closely related but well-differentiated.
Tool names use a mix of underscores and hyphens (e.g., codegen-figma_to_code, design_system-get_files, project-get_git_token) and inconsistent verb placement, making the set appear chaotic.
9 tools is a reasonable number for the dual focus on code generation and playground lifecycle, though the design system tools are somewhat peripheral and increase the count slightly.
Core workflows (Figma to code, playground CRUD, publish/unpublish) are covered, but missing delete/listing of playgrounds and design system documentation is read-only, leaving notable gaps.