Expose your REST APIs to AI agents without building MCP servers
AI agents reach your systems through MCP. G8 serves an API you already run as MCP tools from its OpenAPI document, on a Route with your authentication, rate limits and logs. The conversion runs at the gateway, in your own infrastructure.
Every API an agent needs becomes another server to run
Teams that give AI agents access to internal APIs often write an MCP server for each one. Each server is code to maintain, and it sits beside the rules the API already has.
A server for every API
Each MCP server is written, deployed and patched on its own, and it has to change whenever the API changes.
With G8G8 builds the tools from the OpenAPI document the API already has. The API itself doesn’t change.
Rules that don’t carry over
A server written beside the API often has its own sign-in and no rate limits.
With G8The MCP endpoint is a Route. The authentication and limit Plugins you already use run on it.
Calls nobody sees
Calls from agents don’t show up where the team looks at API traffic.
With G8MCP requests appear in Traffic Explorer and in the logs you already send, like any other request.
An MCP gateway for the APIs you already run
Three parts of G8 work together: the openapi-to-mcp Plugin, the Plugins on the Route and the gateway’s own request records.
From an OpenAPI document to MCP tools
Add the openapi-to-mcp Plugin to a Route and point it at the API’s OpenAPI document. MCP clients connected to the Route list the API’s operations as tools and call them.
- One formSet where the document and the service are, the transport and the headers sent with every call.
- No separate MCP serverThe G8 engine does the conversion, inside your infrastructure.
Your identity and limits on the MCP Route
Put an authentication Plugin and a rate limit on the Route, and MCP clients sign in and are counted like any other client. The Route’s request path shows the order the Plugins run in.
- Authentication firstkey-auth, jwt-auth or openid-connect runs before openapi-to-mcp.
- Limits per clientlimit-count and limit-req count MCP requests like any other requests.
Every call an agent makes, on record
The gateway records MCP requests like any other request. Search them in Traffic Explorer by Route, Consumer or path, and open a record to see its headers and timing.
- Masked before it’s storedHeaders such as authorization and cookie are masked by default.
- Changes on record tooChanges to the Route and its Plugins are written to the audit log.
An internal assistant that works with orders
A typical setup, drawn to show how the parts fit together. It doesn’t describe a specific customer.
A company wants its internal assistant to look up and cancel orders. The orders API already has an OpenAPI document and runs behind G8.
The team adds a Route with openapi-to-mcp pointed at the orders API’s document. The assistant lists the API’s operations as tools.
key-auth gives the assistant its own key, and limit-count sets how many requests it may send.
The assistant’s calls appear in Traffic Explorer, and changes to the Route appear in the audit log.