FORGE turns an API description into an MCP server. The description is the integration.
what it does
A JSON spec names the endpoint, authentication method, operations and parameters an agent may use. FORGE validates that spec, builds the tool schemas and serves the tools over stdio. REST and GraphQL share the same runtime, so adding a vendor means describing its API rather than copying another server.
Credentials stay in environment variables. Parameter descriptions pass through to the tool schema, where the model can use them instead of guessing whether a field expects a name, an identifier or something else.
where writes stop
A tool marked as a write does not execute on its first call. FORGE renders the exact request, shows the destination and payload, hashes that request and returns a confirmation token. The second call must return the same token with the same request.
Changing an argument invalidates the approval. Tokens expire and cannot be reused. Header names appear in the preview; secret values do not.
what is proven
The included Greenhouse spec calls its public REST API in live tests. The Boulevard spec describes a GraphQL booking flow and passes the offline validator, but it has not run against a tenant because the repository has no tenant credentials.
where it stops
FORGE serves one spec per stdio process. It does not add pagination or retries, and it does not claim the offline GraphQL example has been smoke-tested live.