Zoo Mcp
Let a coding agent call Zoo (KittyCAD) CAD API operations through MCP while you design hardware-oriented workflows.
Overview
zoo-mcp is an MCP server for the Build phase that connects agents to KittyCAD Zoo API CAD operations over stdio.
What is this MCP server?
- stdio MCP server for Zoo API CAD operations and tools
- PyPI package zoo_mcp (registry 0.9.1, server 0.9.2)
- Requires ZOO_TOKEN API key from zoo.dev developer account
- Backed by KittyCAD open-source repository on GitHub
- Exposes CAD-oriented capabilities to MCP hosts (Cursor, Claude Code, etc.)
- Server version 0.9.2
- PyPI package zoo_mcp version 0.9.1
- Required secret env ZOO_TOKEN
What problem does it solve?
CAD workflows break agent momentum when every Zoo API call needs custom code and manual auth handling in the chat.
Who is it for?
Indie builders blending software agents with mechanical or parametric CAD on Zoo/KittyCAD.
Skip if: Pure content or web-only products with no CAD API dependency.
What do I get? / Deliverables
After you add ZOO_TOKEN and register zoo-mcp, your agent can invoke Zoo CAD tools as first-class MCP capabilities.
- Agent-callable Zoo CAD API tools via MCP
- Authenticated access to Zoo cloud CAD services
- Reduced custom HTTP glue for CAD automation
Recommended MCP Servers
Journey fit
How it compares
CAD API MCP integration, not a generic 3D asset marketplace skill.
Common Questions / FAQ
Who is zoo-mcp for?
Developers using MCP agents who need programmatic access to Zoo CAD APIs from KittyCAD.
When should I use zoo-mcp?
Use it during build when your agent should create, inspect, or drive CAD operations through Zoo instead of one-off API scripts.
How do I add zoo-mcp to my agent?
Install the PyPI zoo_mcp stdio server, set the required ZOO_TOKEN environment variable from https://zoo.dev/account/developer, and register it in your MCP client config.