Meshy MCP

Generate 3D inside your agent

Run Meshy locally in Claude Code, Cursor, Codex and other clients that support stdio MCP servers, using your Meshy API key.

Set up in one command

Requires Node.js 18 or later and a Meshy API key. Choose a local client, then ask your agent to install the server or use the manual setup.

1

Add the server

Already in a session with Claude Code, Cursor or Codex? Paste this and it will handle the setup.

text
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.
2

Activate and verify

Nothing to do — it loads on your next message.

Verify with

What's my Meshy credit balance?

Then just ask for the model you want.

Using ChatGPT? Find Meshy in the ChatGPT app directory and follow its connection steps. The local MCP configuration above is for desktop and terminal clients. Open ChatGPT apps

Paste this into your prompt and the agent reads the full tool reference itself.

One conversation, a finished asset

Describe your goal in a connected local MCP client. The agent can call Meshy tools to generate, process and download the result.

Describe what you need

What your agent can do now

One connection puts 24 Meshy tools in the conversation — generation is only the start.

Brainstorm before you build

Brainstorm before you build

Explore ideas in conversation, then generate 2D references or 3D models when ready. Image and 3D generation both use API credits.

Batch out whole sets

Batch out whole sets

One prompt, a full prop set — crates, signs, baskets and chests, ready for your level.

Turn anything into 3D

Turn anything into 3D

Text, photos and sketches become textured meshes — or clean sculpts for printing.

It knows 3D

It knows 3D

Formats, printability, broken meshes — the tools carry the know-how, so the agent answers and fixes instead of guessing.

24Meshy tools

One connection, and every one of them is callable by name.

Built for Every 3D Workflow

From a single chat, the agent slots into the pipeline you already run — games, 3D printing, and product design — exporting the right format for each.

meshy_text_to_3d
Chibi ice dragon character sculpt in cartoon style

Frequently asked questions

Model Context Protocol is an open standard for connecting AI agents to external tools and data. An MCP server exposes a set of tools, and any MCP-compatible client can call them. Meshy publishes one for 3D generation.

The local server has setup instructions for Claude Code, Cursor, Codex, Windsurf, VS Code and Claude Desktop. Other clients need stdio MCP support. ChatGPT uses its existing Meshy app directory entry, with its own connection instructions.

Yes. The server authenticates with a Meshy API key, which requires a Pro plan or above. Create one in your account settings and pass it as MESHY_API_KEY.

Calls use the Meshy API credit rules for the selected operation and options. Check the current API pricing documentation and use meshy_check_balance before a paid workflow. Image generation also consumes credits.

The plugins put Meshy inside a specific 3D application, driven by you clicking. The MCP server puts Meshy inside an AI agent, driven by the agent deciding. Plenty of people run both.

Duration depends on the task, model and queue. Most generation tools return a task ID; meshy_get_task_status can wait for completion. Creative Lab workflows can wait for multiple stages within one tool call.

Cursor and VS Code need a manual toggle after install — see the activate step for your client above. On Claude Code and Gemini CLI, run /mcp to list connected servers. If the tools still do not appear, check that mcp.json is valid JSON with no trailing commas, and that MESHY_API_KEY sits inside an env block rather than in args.

Yes. If npx fails to spawn, wrap the command with cmd /c. On Claude Code for Windows, use claude mcp add-json rather than the flag form.

Commercial rights follow your Meshy plan, not the interface you generated through. Paid plans include commercial licensing.

The npm MCP server runs locally with your API key. This page does not provide a hosted MCP URL. The separately published meshy-cli calls the REST API directly and supports browser sign-in; it does not require the MCP server.

Name the server meshy — every config on this page does — and say so in the prompt: “use Meshy to…”. Agents route by tool descriptions, and naming the product is the most reliable disambiguation.

MCP-generated assets belong to the API account, not the Meshy web workspace, and do not automatically appear in My Assets. Download URLs expire, so save results you want to keep. Use the API console for API task history and usage.

Each user configures their own API key. This local server does not provide shared organization login or multi-user credential isolation.