Zoo MCP Server

If you already use Zoo, the zoo mcp server is the piece that lets your assistant work with it directly. An MCP server that provides access to the Zoo API for various CAD operations and tools.

What the server does

An MCP server housing various Zoo built utilities

Installation

The server ships on PyPI as zoo-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: ZOO_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

1. An API key for Zoo, get one here 2. An environment variable ZOO_API_TOKEN set to your API key

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by KittyCAD; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Zoo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.