Home
Documentation
AI Gateway
MCP Servers

MCP Servers

Expose corporate APIs and existing MCP Servers as endpoints governed by the gateway.

The MCP Servers module exposes MCP Servers: access points compatible with the Model Context Protocol that AI agents can invoke as tools, always under the governance, authentication, and observability of AI Gateway.

Each MCP Server is registered from one of two origins:

From an API: the gateway generates and hosts an MCP translator from an API revision published in the Sensedia Platform multigateway catalog. A set of MCP Configs decides which API endpoints are exposed and how: as a tool, resource, resource template, or excluded.
From an existing MCP Server: the gateway acts as a proxy in front of an MCP Server that already exists, internal to your company or third-party, without rewriting, migrating, or re-hosting anything. You choose which tools from that server you want to expose to your agents.

NOTE
Prerequisites depend on the chosen origin. For From an API, you need a REST API published in the Sensedia Platform catalog. That catalog is fed by the connections configured in Connections: create a connection to your API Gateway there so its APIs become available in the selection. For From an existing MCP Server, you need the remote server address and, when it requires authentication, a valid credential. In both cases, to restrict access to the MCP Server by scopes, register the scopes in the Scopes catalog first.

Quick links

Learn how to:

Filter and list MCP Servers
Create an MCP Server
Edit an MCP Server
Delete an MCP Server
Review the fields common to both origins
Configure the From an API origin
Configure MCP Configs
Configure the From an existing MCP Server origin
Select the exposed tools

Listing

The MCP Servers page lists registered servers with pagination. You can filter by:

Source (optional): MCP Server origin. Values: All sources, From an API, External MCP.

Use Search to apply the filter and Clear to reset it.

Columns shown in the table:

Transport: configured transport protocol (SSE or Streamable HTTP).
Source: MCP Server origin (From an API or External MCP).
Exposed Endpoint: public path exposed by the gateway. It is used by the MCP Clients that connect to this MCP Server.
Tools / Configs: for the From an API origin, a summary of the exposure configurations in the TYPE (methods:..., tags:..., regex:...) format per block; for the From an existing MCP Server origin, the list of exposed tools, or the All tools label when no selection was made. Shows No MCP configs. if empty.
Scopes: list of associated scopes, resolved to the name registered in Scopes. Shows No scopes assigned. if empty.
Created At: creation date and time in your time zone.
Actions: Edit and Delete icons for each row.

Create MCP Server

Step 1

On the MCP Servers page, click Create MCP Server.

Step 2

Choose the Origin: From an API or From an existing MCP Server. This choice defines which form sections are displayed.

Step 3

Fill in the common fields: Exposed endpoint, MCP transport, and, to restrict access, Scopes.

Step 4

Fill in the section specific to the chosen origin: From an API (authentication, API selection, and MCP Configs) or From an existing MCP Server (remote server address and tool selection).

Step 5

Click Save to confirm the registration. To discard, click Cancel.

Edit MCP Server

In the Actions column of the row you want, click the Edit icon. The Update MCP Server form opens prefilled and with the section matching the server's origin. Change the required fields and click Save.

Delete MCP Server

In the Actions column of the row you want, click the Delete icon. Confirm the operation in the "Do you want to delete MCP server [mcpServerId]?" dialog.

IMPORTANT
Deletion is permanent and cannot be undone. Agents already using this MCP Server start failing on subsequent calls.

Fields common to both origins

Field	Type	Required	Rules
Origin	Origin selection	Yes	From an API — Generate and host an MCP translator from a catalog API. From an existing MCP Server — Register an existing MCP server and proxy it through AI Gateway.
Exposed endpoint	Text	Yes	Public path the gateway exposes to the MCP client.
MCP transport	Select (enum)	Yes	Values: SSE (Server-Sent Events) and Streamable HTTP.
Scopes	Multi-select	No	List of scope IDs from the Scopes catalog required in the client's access token. Select zero or more scopes. An empty list means any authenticated token can invoke the MCP Server.

Origin: From an API

In this origin, the gateway generates the MCP Server from an API revision in the catalog. In addition to the common fields, the form displays the authentication, API Selection, and MCP Configs sections.

Authentication mode

The Authentication mode field defines how the MCP Server authenticates when calling the business API:

Mode	Behavior
Client credentials	The MCP Server obtains its own access token (`client_credentials`) and uses it to call the API.
Passthrough	The MCP Server forwards to the API the token of the end user logged into the agent, enabling scenarios where the API needs to identify the user to apply its own access rules.

Each mode displays its own set of fields:

Field	Type	Required	Rules
MCP server client ID	Text	Yes — Client credentials mode	Client ID used to obtain the access token the MCP Server uses to access the API.
MCP server client secret	Text (sensitive, password)	Yes — Client credentials mode	Client Secret matching the MCP server client ID.
OAuth token URL	Text	Yes — Client credentials mode	URL of the OAuth token endpoint used to obtain the access token.
Input header	Text	Yes — Passthrough mode	Header sent by the agent carrying the end user's credential.
Output header	Text	Yes — Passthrough mode	Header in which the credential is forwarded to the API.

THE SETS ARE EXCLUSIVE
The fields of one mode are not accepted in the other. In Passthrough, filling in any of the three OAuth fields results in a validation error (Not allowed for passthrough authentication.). In Client credentials, the same applies to Input header and Output header (Not allowed for client credentials authentication.).

API Selection

Field	Type	Required	Rules
API	Searchable select	Yes	Lists the APIs available in the Sensedia Platform multigateway catalog (not typed freely). The set shown depends on the connections previously configured in Connections. Only APIs from gateways reachable through those connections appear.
Revision	Select	Yes	Lists the revisions of the selected API, also fed by the multigateway catalog. Disabled until an API is chosen.
API base URL	Text	Yes	Base URL of the target API, where the gateway forwards the MCP agents' calls.

REST APIS ONLY
The API selector lists only REST APIs. MCP Server generation starts from the API's OpenAPI contract to build the tools, so GraphQL, gRPC, HTTP, and Event APIs do not appear in this list. To expose one of those cases, use the From an existing MCP Server origin.

MCP Configs

Section exclusive to the From an API origin. This is a required list with at least one block. Each Config block describes which API endpoints are included in the MCP Server and how. This lets you expose only the desired API endpoints to MCP clients.

Use Add config to add blocks and the delete icon to remove them (disabled when there is only one).

REQUIRED COMPLETION
Within each Config, at least one of Methods, Tags, and Endpoint regex must be filled in.

Fields per config

Field	Type	Required	Rules
Methods	Multi-select (HTTP methods)	Conditional: individually optional; required if Tags and Endpoint regex are empty	Selectable values: GET, POST, PUT, PATCH, DELETE. Defines which verbs of the API endpoints are exposed in the MCP Server.
Tags	List of tags	Conditional: individually optional; required if Methods and Endpoint regex are empty	List of OpenAPI tags whose API endpoints are exposed in the MCP Server. Each tag must have at least 1 character.
Endpoint regex	Text	Conditional: individually optional; required if Methods and Tags are empty	Regular expression validated against the API endpoint paths. Minimum 1 character (when provided).
Type	Select (enum)	No	Values: Tool, Resource, Resource template, Exclude. When empty, the gateway assumes TOOL.

Meaning of the types

Type	Meaning
Tool	The endpoint is exposed to the agent as a tool it can invoke.
Resource	The endpoint is exposed as a static resource (read-only).
Resource template	The endpoint is exposed as a parameterizable resource (URI template).
Exclude	The endpoint is not exposed to the agent. Useful for removing specific items when the filter includes a broad set (for example, include everything from a tag, except one endpoint).

Origin: From an existing MCP Server

In this origin, the gateway forwards calls to an MCP Server that already exists. In addition to the common fields, the form displays the External MCP Server section and the Tools section.

External MCP Server section fields

Field	Type	Required	Rules
Host	Text	Yes	Bare hostname of the remote server: without `http://` or `https://`, without a path, and without a port. The path goes in Upstream path and the port in Port.
Port	Integer	No	Between 1 and 65535. When empty, it assumes 443.
Upstream path	Text	No	Path of the MCP on the remote server. When empty, it assumes the default for the selected transport.
Upstream authentication	Select (enum)	No	None: the remote server requires no credential. Passthrough: the end user's credential is forwarded to the remote server.
Header	Text	Yes — Passthrough mode	Inbound header carrying the user credential to be forwarded.

Tools

The Tools section defines which tools from the remote server are visible to your agents. To fill it in, the gateway connects to the server and lists what it offers.

Step 1

Fill in Host, Port, Upstream path, and the Discovery credential. While these fields are incomplete, the Fetch tools button stays disabled.

Step 2

Click Fetch tools. The gateway connects to the remote server and brings back the list of available tools.

Step 3

In Exposed tools, select the tools you want to expose. Use the search field to locate items in long lists.

Field	Type	Required	Rules
Discovery credential	Text (sensitive)	No	Token used only to list the remote server's tools. It is not saved with the MCP Server. It serves only for the lookup.
Exposed tools	Searchable multi-select	No	List filled in by Fetch tools. *Leaving the selection empty exposes all tools* from the server.**

AN EMPTY SELECTION EXPOSES EVERYTHING
If you do not select any tool, the MCP Server exposes all tools from the remote server, and the listing shows the All tools label. To restrict what agents can see, explicitly select the desired tools.

IF THE CONNECTION FAILS
When the gateway cannot connect, the message Could not connect to the MCP server to list its tools. Check the host, port, path, transport, and credential. is displayed. Review those five fields, especially the Host, which must be the bare hostname, without a path, port, or protocol. If the server responds but offers no tools, the section shows The server returned no tools.

How happy are you with this page?

Policies

AI Agents