Overview
The Meshy MCP (Model Context Protocol) server lets local AI agents — such as Claude Code, Cursor, Codex, and any other client that supports stdio MCP servers — call Meshy's 3D tools directly from a conversation.
One connection gives your agent 24 Meshy tools: text to 3D, image to 3D, texturing, remeshing, rigging, printability checks, downloads, and more. For the full setup page, see meshy.ai/mcp.
Meshy 3D Agent vs. Meshy MCP
Meshy 3D Agent runs inside meshy.ai in your browser — no setup needed.
Meshy MCP brings the same generation tools into the AI client you already work in, so you can create and download 3D assets without leaving your editor or terminal.
What You Need
Node.js 18 or later
A Meshy API key — create one in the Meshy Developer Platform
Setup
Option A: Let your agent install it (recommended)
In a Claude Code, Cursor, or Codex session, paste:
Install the Meshy MCP server for me. Docs: https://github.com/meshy-dev/meshy-mcp-server Help me configure MESHY_API_KEY locally in the client settings. Do not ask me to paste an API key into this chat.
Option B: Manual setup
Follow the manual steps for your client on meshy.ai/mcp or in the GitHub README.
Verify the connection
The server loads on your next message. Ask your agent: "What's my Meshy credit balance?"
If it answers, you're connected — just describe the model you want.
Using ChatGPT?
Add Meshy 3D from ChatGPT Plugins and sign in with your Meshy account. No API key or local setup is needed, and it works on both web and desktop.
Credits and Security
Generations made through MCP use API credits from the account linked to your API key, just like direct API calls.
Treat your API key like a password: never paste it into a chat, and don't commit it to source control or shared config files.
Learn More
Tutorial: Using the Meshy API and MCP
All integrations: meshy.ai/integrations
Docs for AI agents: docs.meshy.ai/api/ai.md
FAQ
1. Is the MCP server the same as the Meshy Agent in the browser?
No. Meshy 3D Agent is the chat interface on meshy.ai. The MCP server exposes Meshy's tools to external AI clients like Claude Code, Cursor, or Codex.
2. My client doesn't list the Meshy tools. What should I do?
Check that Node.js 18+ is installed and that MESHY_API_KEY is set in the client's MCP settings, then restart the client. See the troubleshooting section of the GitHub README.
3. Do MCP generations use the same credits as the web app?
They use the API credits on the account that owns your API key.
4. Where do the generated models go?
Ask the agent to download the format you need, for example GLB or FBX. Local downloads are saved under meshy_output/, ready for your DCC app or slicer.
5. Can I reuse one API key across several tools?
Yes, across clients you trust — but keep it out of shared or public config files.