Connect Claude Desktop or Codex over MCP

Updated Nov 16, 2026 · 4 min read

Let Claude Desktop or Codex search your 3D model library over MCP: turn it on in Settings → Integrations, pick what each one sees, and paste its configuration.

Meshory has a built-in MCP server, so an AI assistant on this computer can search your 3D model library and answer questions about it: what you own, which models have no tags yet, what's on a print list. Claude Desktop and Codex are the apps its settings name. Each assistant gets its own connection, which sees only the sources, folders and collections you share, and nothing it suggests changes your library until you approve it.

Assistant connections arrive in the Meshory release after 1.13.0. They need an activated license, and Meshory must be running while the assistant uses it.

Add a connection

  1. 1Open Settings → Integrations and choose the Local tab.
  2. 2Turn on Enable MCP. It's off by default.
  3. 3Type a name such as Claude Desktop in New connection name and click Add connection. Add one connection per app, so each has its own access.
  4. 4Under Shared sources, folders and collections, pick what the assistant may see. Selections combine, and a folder includes every folder inside it.
  5. 5Under What it can do, tick what the assistant can read and what it can propose. Library details (model names, descriptions and tags) is the base every connection needs.
  6. 6Switch on Enable connection and click Save connection.
  7. 7Under Set up in your app, click Copy configuration, then add it to the assistant as described below.

Claude Desktop

In Claude Desktop, open Settings → Developer and click Edit Config, which opens claude_desktop_config.json. Paste the JSON configuration Meshory copied. If the file already lists other servers, add the meshory entry inside its existing mcpServers block rather than replacing the file. Save it, then quit and reopen Claude Desktop.

Codex

Switch the configuration to Codex TOML, click Copy configuration, and paste it into config.toml in your .codex folder (~/.codex/config.toml on macOS and Linux), creating the file if it isn't there. Start a new Codex session to load it.

Either way, the configuration starts meshory-bridge, a small helper installed with Meshory. The assistant runs it on this computer, and it talks to the running Meshory app directly, not over the internet.

Connection status

What an assistant can do

What it can do has two columns. Can read lets the assistant see something; Can propose lets it suggest a change that waits for you. Leave every Can propose box empty and the connection is read-only.

Every suggestion waits under Settings → Integrations → Approvals until you approve or reject it: see Approving what an assistant suggests. Conversions and slicer handoffs are covered in Assistant jobs.

What leaves your computer

Meshory gives the assistant model details, never the model files: the names, descriptions and tags of what you shared, plus the favourites, print lists and reports you allowed. The assistant passes what it reads to the AI service behind it, Anthropic for Claude Desktop and OpenAI for Codex, under that service's terms. Meshory sends nothing to those services itself.

Sharing narrows what a connection can see through Meshory. It isn't a sandbox: other programs running as you on this computer can still access your local files.

Change or remove a connection

Edits apply when you click Save connection, and narrowing what's shared takes effect straight away. Remove connection… ends its access at once; to use that app again, add a new connection and paste its new configuration. You can have up to 32 local connections.

Did this page help?

Still stuck? Ask in the Discord