The Allyson MCP Server is an AI-powered tool that transforms static images into animated SVG components using the Model Context Protocol (MCP).
Key capabilities:
Generate animated SVGs from static files (PNG, JPG, SVG)
Define animations using natural language prompts
Process local files using absolute paths
Save animated components to specified locations (e.g., in TSX format)
Integrate with MCP-compatible AI assistants and tools like Claude Desktop and Cursor IDE
Provide secure handling of API keys with HTTPS communication
Runs on Node.js version 18.0.0 or higher, utilizing it as the runtime environment for the animation generation server.
Available as an npm package (allyson-mcp) that can be installed and run using npm or npx commands.
Enables AI-powered transformation of static SVG files into animated SVG components with custom animation effects like glowing, pulsing, spinning, and bouncing.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Allyson MCP Server animate my logo to pulse gently and save it as AnimatedLogo.tsx"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Allyson MCP Server - AI-powered animation generator that transforms static files into animated SVG components using the Model Context Protocol (MCP).
npx allyson-mcp --api-key YOUR_API_KEYRelated MCP server: @excalimate/mcp-server
allyson-mcp [options]
Options:
--api-key <key> Your Allyson API key (required)
--help Show help message
Examples:
allyson-mcp --api-key your-api-key-here
API_KEY=your-key allyson-mcpYou can also set your API key as an environment variable:
export API_KEY=your-api-key-here
allyson-mcpAI-Powered Animation Generation: Transform static images into animated SVG components
MCP Protocol Compatible: Works with any MCP-compatible AI assistant or tool
File Upload Support: Supports various image formats (PNG, JPG, SVG, etc.)
Custom Animation Prompts: Describe exactly what animation you want
Local File Processing: Reads files from your local filesystem
Automatic Output Generation: Saves animated components to specified paths
generate_svg_animationGenerates an animated SVG component from a source file and animation prompt.
Parameters:
prompt (string, required): Description of the animation to generate
Example: "Make the character wave their hand"
Example: "Add bouncing motion to the ball"
Example: "Create a spinning effect for the logo"
svg_path (string, required): Absolute path to the source file
Example: "/path/to/my-icon.svg"
output_path (string, required): Absolute path where to save the animated component
Example: "/path/to/animated-component.tsx"
Example Usage in MCP Client:
{
"tool": "generate_svg_animation",
"arguments": {
"prompt": "Make the logo glow and pulse gently",
"svg_path": "/Users/john/Desktop/company-logo.svg",
"output_path": "/Users/john/project/src/components/AnimatedLogo.tsx"
}
}This MCP server is designed to work with AI assistants that support the Model Context Protocol, such as:
Claude Desktop (with MCP configuration)
Cursor IDE (with MCP integration)
Custom AI Applications (using MCP SDK)
{
"mcpServers": {
"allyson": {
"command": "npx",
"args": ["allyson-mcp", "--api-key", "YOUR_API_KEY"]
}
}
}# Start the server
allyson-mcp --api-key your-api-key
# The AI assistant can now use the tool:
# "Please animate this logo to have a subtle glow effect"
# File: /Users/john/logo.svg → /Users/john/animated-logo.tsxAPI Key Protection: Your API key is securely transmitted to the Allyson service
Local File Access: Only reads files you explicitly specify
No Data Storage: Files are processed and not stored on external servers
HTTPS Communication: All API communications use secure HTTPS
"API key is required" Error
# Solution: Provide API key via flag or environment variable
allyson-mcp --api-key YOUR_KEY
# or
export API_KEY=YOUR_KEY && allyson-mcp"File not found" Error
# Make sure to use absolute paths
❌ Wrong: ./image.svg
✅ Correct: /Users/username/project/image.svg"Cannot connect to animation API server" Error
Check your internet connection
Verify your API key is valid
Ensure the Allyson service is accessible
Permission Issues
# Make the file executable if needed
chmod +x node_modules/allyson-mcp/index.jsFor debugging, you can check the server logs which are output to stderr:
allyson-mcp --api-key YOUR_KEY 2> debug.logNode.js: Version 18.0.0 or higher
API Key: Valid Allyson API key
Internet Connection: Required for API communication
We welcome contributions! Please see our contributing guidelines for more details.
Apache-2.0 License - see LICENSE file for details.
Documentation: Check this README and inline help (--help)
Issues: Report bugs on our GitHub Issues
Generate an SVG animation from a source file and prompt
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | Description of what animation to generate (e.g., 'Make the character wave their hand', 'Add bouncing motion to the ball') | |
| svg_path | Yes | Local file path to the source file to animate, must be the absolute path (e.g., '/Users/username/image.svg') | |
| output_path | Yes | Local file path to the output file, must be the absolute path (e.g., '/path/to/animated-svg.tsx') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full responsibility for disclosing behavioral traits. It omits critical details such as whether the tool modifies the input file, what happens to existing files at output_path, or any requirements for the SVG content. The sparse description leaves much to inference.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (one sentence, nine words), which is acceptable for a simple tool. However, it lacks structure (e.g., no front-loading of important constraints or behaviors) and could be slightly expanded to improve usability without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's generative nature, the description is incomplete. It does not explain the output animation format, any side effects, or potential limitations. Without an output schema, the agent receives no information about what the tool returns, leaving a significant gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers 100% of parameters with clear descriptions. The tool description adds no additional meaning beyond the schema, but the schema itself is sufficiently descriptive for each parameter, making the baseline score appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Generate an SVG animation' and identifies the resources ('from a source file and prompt'). It is specific enough to convey the core functionality without confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives (though none are listed), nor does it mention any preconditions or exclusions. It only states what the tool does, not when it should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.5generate_svg_animation1 field changedInput schema / properties / svg_path / descriptionPrevious value: -"Local file path to the source file to animate, must be the absolute path (e.g., '/Users/username/image.png')"New value: +"Local file path to the source file to animate, must be the absolute path (e.g., '/Users/username/image.svg')"v1.0.0generate_svg_animationWith only one tool, there is no possibility of confusion between tools. The single tool has a clear purpose.
The single tool name 'generate_svg_animation' uses a clear snake_case verb_noun pattern. Consistency is not an issue with one tool.
The server has only one tool, which is borderline for a server with a generic name. However, if the server's sole purpose is generating SVG animations, the count is justifiable but feels minimal.
The single tool covers the primary operation of generating an SVG animation from source and prompt. Minor gaps exist, such as no tool for listing or managing animations, but for a focused tool it is acceptable.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Turn words, images, and audio into an animated video with MP4 export.
Create AI animations and export transparent sprite sheets, alpha video, frames, and game assets.
Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.
Create consistent mascot assets and animations for products through AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/isaiahbjork/allyson-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
