MCP SERVER · AGENT TOOLING
32 tools·Streamable HTTP·18 OEM families·Free tier
A cross-vendor industrial MCP server. Connect any AI agent to any machine on any factory floor, without writing an adapter per manufacturer.
Streamable HTTP at https://mcp.foundrynet.io/mcp. Works with Claude Code, Claude Desktop, Bedrock AgentCore Gateway and any MCP client.
MCP standardised how an agent calls a tool. It did not standardise what a Fanuc controller calls its spindle speed, and it never intended to. Wiring an agent to a factory still means an adapter per manufacturer, a mapping table per controller and a maintenance burden that grows with the fleet.
Forge exposes that whole translation layer as a single MCP server. One connection covers 18 OEM families and 14 protocols, and the tool surface is the same regardless of whose machine is on the other end.
Transport is Streamable HTTP at https://mcp.foundrynet.io/mcp. Authentication is a Bearer API key. There is a free tier, and the free tool set is identical over MCP and REST — the transport does not change what you can reach.
Forge and Assay are both listed as SaaS products with metered usage. Subscribe through your existing AWS account and bill on your AWS invoice.
Reachable from AgentCore via the published OpenAPI specification. Note that AgentCore rejects oneOf/anyOf/allOf, so the spec is served in a flattened form for it.
Claude Code, Claude Desktop, and anything else speaking Streamable HTTP. Point at the canonical endpoint rather than a redirecting vanity host — cross-host redirects can drop the Authorization header.
Every tool has a REST equivalent under https://forge.foundrynet.io/v1/. Same auth, same free tier, same responses.
Longer-form writing on industrial AI infrastructure by Foundry Labs.