MCP HTTP Bridge plugin
The MCP HTTP Bridge plugin lets an agent use a plain REST API through an MCP route. The agent sees MCP tools. When the agent calls one, the gateway turns the call into a real HTTP request to the REST API and returns the response as the tool result.
The control plane builds the tools from the OpenAPI spec that you imported when you created the REST connection. You choose which operations become tools, and you can rename them. The data plane applies the result and never reads the spec. Authentication, tool prefixing, filtering, redaction, and billing on the MCP route work as for any other MCP connection.
Where it runs
Set up the plugin
The console has no form for this plugin. You compile the tools and save the instance with the admin API.
Prerequisites
Before you begin, make sure you have the following:
- A REST connection that you created by importing an OpenAPI spec. For the steps, see Import an OpenAPI spec. A connection that you added by hand has no stored spec, so compiling it fails with
404. - An MCP route that uses that connection.
- An admin API key and your tenant ID. For the steps, see Configure the gateway with the admin API.
- A list of the operations to expose, as
METHOD /pathkeys such asGET /pets. The plugin exposes nothing that you don’t list.
Steps
-
Preview the configuration. Send the name of the REST connection and the operations to expose to the compile endpoint:
Nothing is saved. The response has the
configto save, the list ofoperationswithincludedflags,warnings, operations the compilerskipped, and adiffagainst the earlier compile. An emptyincludereturns a warning and no tools. -
Review the
operations,warnings, andskippedfields. To rename a tool or change its description, setnameordescriptionfor the operation ininclude, and compile again. Tool names use letters, digits,_, and-, up to 64 characters. -
Save the instance. Send the
configobject from the compile response unchanged:The control plane checks the configuration when you save it, and returns
400with the reason if it’s invalid. Data planes pick up the change a moment later. -
To pick up changes to the REST API, import the updated spec again, and then repeat the compile and save. Operations that you add to the spec later appear in the
diffas new and stay off until you include them. To update the saved instance, send the new configuration withPUT.
Verify it works
To check that the route serves the tools, do the following:
- Send
tools/listto the MCP route with your usual MCP credentials. The result lists exactly the tools that you included. - Send a
tools/callfor one tool, with arguments that match its input schema. The result holds the REST API’s response body as text. - Send a
tools/callwith an argument that breaks the schema. The result hasisErrorset totrue, and the REST API isn’t called.
For a command-line client, use the MCP Inspector:
Fix common problems
Configuration
Don’t write this configuration by hand. The compile endpoint builds it from the spec, and the control plane rejects a saved configuration that doesn’t match its curation.
The name of the REST connection on the route that the tools front.
The tools to expose, at most 200. Names must be unique.
The tool name that the agent sees.
The tool description that the agent sees.
The JSON Schema for the tool’s arguments. The gateway validates every call against it. References to files or URLs outside the schema are rejected.
The HTTP method: GET, POST, PUT, PATCH, DELETE, or HEAD.
The request path template, such as /pets/{petId}. It must start with /, and every placeholder needs a path argument.
Maps each input property to where its value goes in the request. in is path, query, or body. Header arguments aren’t supported. A query argument can use the form or deepObject style. Body arguments nest into one JSON object, and an argument with an empty name is the whole body.
Your choice of operations, which the control plane keeps so that it survives spec updates. include maps an operation key to optional name and description overrides. seen records the operations from the last compile. The data plane ignores it.
An instance can be at most 1 MiB, curation included, because every data plane receives it. For each call, the gateway rotates through the connection’s upstreams, skips any that are pin-only, sends the request with the connection’s credential and timeout, and doesn’t follow redirects. It returns a 2xx body as text, and a 4xx or 5xx response as an error result with the status and body. A response over 4 MiB returns “upstream response too large”. If no upstream is left, the call fails with service "<name>" has no routable upstream.

