MCP server for Meshy AI 3D generation platform
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"meshy": {
"env": {
"MESHY_API_KEY": "msy_YOUR_API_KEY"
},
"args": [
"-y",
"@meshy-ai/meshy-mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Model Context Protocol (MCP) server for the Meshy AI 3D generation platform. Enables AI agents to create, manage, and download 3D models, textures, images, rigged characters, and animations through natural conversation.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / design
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
MCP Security Weekly
Get CVE alerts and security updates for Meshy Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol (MCP) server for the Meshy AI 3D generation platform. Enables AI agents to create, manage, and download 3D models, textures, images, rigged characters, and animations through natural conversation.
20 tools covering the full Meshy API:
| Category | Tools |
|---|---|
| 3D Generation | meshy_text_to_3d, meshy_text_to_3d_refine, meshy_image_to_3d, meshy_multi_image_to_3d |
| Post-Processing | meshy_remesh, meshy_retexture, meshy_rig, meshy_animate |
| Image Generation | meshy_text_to_image, meshy_image_to_image |
| Task Management | meshy_get_task_status, meshy_list_tasks, meshy_cancel_task, meshy_download_model |
| Workspace | meshy_list_models |
| 3D Printing | meshy_send_to_slicer, meshy_analyze_printability, meshy_repair_printability, meshy_process_multicolor |
| Account | meshy_check_balance |
analyze_printability — free FDM check (watertight, volume, holes, non-manifold edges, degenerate faces)repair_printability — 10-credit topology repair (output format mirrors input)process_multicolor — 10-credit multi-color 3MF for AMS/MMU printersmeshy_output/ with project folders, metadata, and history trackingPick whichever fits your workflow — they all produce the same config.
add-mcp auto-detects every AI client on your machine (Cursor, Claude Code, Claude Desktop, Windsurf, Codex, VS Code, Cline, …) and writes the right config to each:
npx add-mcp @meshy-ai/meshy-mcp-server --env MESHY_API_KEY=msy_YOUR_API_KEY
After it finishes, jump to Activate for your client.
Already chatting with Cursor / Claude Code / Codex? Paste this prompt:
Install the Meshy MCP server for me. Docs: https://github.com/meshy-dev/meshy-mcp-server
Use this env var: MESHY_API_KEY=msy_YOUR_API_KEY
The agent will run add-mcp (or write mcp.json directly) and tell you when it's ready. You'll still need the Activate step for your client.
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"meshy": {
"command": "npx",
"args": ["-y", "@meshy-ai/meshy-mcp-server"],
"env": { "MESHY_API_KEY": "msy_YOUR_API_KEY" }
}
}
}
Windows: replace
"command": "npx"with"command": "cmd"and"args": ["/c", "npx", "-y", "@meshy-ai/meshy-mcp-server"].
claude mcp add-json meshy '{"command":"npx","args":["-y","@meshy-ai/meshy-mcp-server"],"env":{"MESHY_API_KEY":"msy_YOUR_API_KEY"}}'
Use Option 1 — add-mcp writes the correct config for each.
Most clients auto-load the new server, but **Cursor and V