Forge MCP

What FoundryNet/forge-mcp MCP server does

FoundryNet/forge-mcp MCP server connects MCP clients to FoundryNet's Forge v1 API for industrial machine intelligence. It is designed for CNCs, robots, and other industrial equipment from different manufacturers. The service presents a common interface for machine identity, telemetry, automation, prediction, operations reporting, guardrails, agent coordination, and work verification.

Telemetry from 18 manufacturer families can be converted into a canonical vocabulary with confirmed field mappings. This lets an agent use consistent field names across equipment such as Fanuc CNCs, KUKA arms, and Universal Robots cobots. The server also supports plain-English automation workflows, where an automation can be created and reviewed before activation.

How it works

FoundryNet/forge-mcp MCP server is a stateless HTTP proxy. An MCP client sends tool requests to the hosted endpoint, and the proxy forwards them over HTTPS to forge.foundrynet.io/v1/* with a configured fnet_ Bearer key. The repository describes the service as a separate Railway deployment with its own dependencies, including FastMCP and HTTPX.

The preferred endpoint uses Streamable HTTP at https://mcp.foundrynet.io/mcp. A legacy Server-Sent Events endpoint remains available at https://mcp.foundrynet.io/sse. Health and server-card endpoints are also provided. Because the proxy has no state of its own, machine and Forge data handling occurs through the upstream API.

Setup and configuration

Create a FoundryNet account and obtain an fnet_ API key, then configure the MCP client with the Streamable HTTP endpoint and an Authorization: Bearer header. Claude Desktop can use the mcp-remote bridge, while clients with native HTTP transport can connect directly. The README provides a Claude CLI example and a Claude Desktop configuration using FNET_KEY.

For a server-side deployment, set FOUNDRYNET_API_KEY. FORGE_BASE_URL defaults to https://forge.foundrynet.io, PORT defaults to 8080, and REQUEST_TIMEOUT defaults to 30 seconds. The API key is required for successful tool calls; the process can boot without it, but requests return 401 until the key is supplied.

Tools and capabilities

The 32 tools are grouped into the following areas:

• Identity and data: identify machines, normalize telemetry, query machine history, inspect coverage, and correct mappings.
• Automation: create, activate, list, disable, delete, and restore automations, plus query webhook history.
• Prediction: forecast values, predict threshold breaches, estimate remaining life, run batch predictions, score fleet health, detect anomalies, inspect machine intelligence, and review prediction accuracy.
• Operations: calculate OEE, calculate fleet OEE, measure energy consumption, produce shift reports, diagnose machines, and calculate a health index.
• Guardrails and agents: check or list guardrails, inspect the connected agents on the kernel, and list those agents.
• Work records and demonstration: verify completed work records or run the fire_sandbox watch-to-settle demonstration loop.

The free tier exposes read-only tools. Premium prediction and diagnostics tools use metered pay-per-use access. Agent-card and agent-list tools cover agents connected to the user's kernel and are not cross-platform discovery tools. verify_record creates a hash-verified, tamper-evident record of completed work.

Limitations and notes

Access depends on a FoundryNet API key and the applicable subscription tier or usage charges. The repository identifies the software as proprietary commercial software owned by Foundry Labs LLC. New integrations should use Streamable HTTP rather than the retained SSE endpoint.