Engineering MCP servers for Claude.
ForgeMCP hosts Maple, GD&T, Creo, and SolidWorks as Model Context Protocol servers — drop one URL into Claude and your engineering tools work natively.
Engineering APIs we host
- Maple
- GD&T
- Creo (soon)
- SolidWorks (soon)
One gateway, three deployment shapes
Hosted
We run the upstream API for you. Single bill, single config, ready in minutes.
BYO
Bring your own keys for Maple / Creo / GD&T. We never see your raw credentials.
Self-hosted
Deploy the gateway into your own Cloudflare account. Same code, your data plane.
Frequently asked
What's the difference between the Claude host (mcp.forgemcp.ai) and the generic MCP host (mcp.forgemcp.ai)?
The Claude host is optimised for the Claude Connectors UI. The generic host is for any MCP-compatible client.
Which tools ship in Phase 1?
Maple compute and GD&T tolerance helpers. Creo and SolidWorks land in later phases.
Can I use my own API keys?
Yes — the BYO tier stores your provider keys encrypted at rest (AES-GCM-256) and uses them on every tool call.
Where does my data go?
Cloudflare Workers in the region closest to your users. No third-party processors beyond the upstream engineering APIs you choose.