The MCP Servers module turns API revisions published in the Sensedia Platform multigateway catalog into MCP Servers: access points compatible with the Model Context Protocol that AI agents can invoke as tools. Each MCP Server combines OAuth credentials, an API revision, and a set of MCP Configs that decide which API endpoints are exposed and how: as a tool, resource, resource template, or excluded.
NOTETo create an MCP Server, you need a valid API Catalog ID and API Revision ID in the Sensedia Platform catalog, plus the OAuth credentials the gateway will use to call the target API. Create a Connection to bring your API Gateway APIs into the catalog and automatically create MCP Servers from the OpenAPI specifications of those APIs. To restrict access to the MCP Server by scopes, register the scopes in the Scopes catalog first.
Learn how to:
The MCP Servers page lists registered servers with pagination. You can filter by:
Use Search to apply the filter and Clear to reset it.
Columns shown in the table:
TYPE (methods:..., tags:..., regex:...) for each block. Shows No MCP configs. when empty.Fill in the credentials (MCP server client ID, MCP server client secret, OAuth token URL), the transport, and the required scopes (see Form fields).
In the API Selection section, choose the API (catalog) and the corresponding Revision, then enter the API base URL and Exposed endpoint that the gateway exposes to the MCP Client.
In MCP configs, configure at least one Config block to define which API endpoints are exposed (see MCP Configs). Use Add config to add blocks.
In the Actions column of the row you want, click the Edit icon. The Update MCP Server form opens with the current data. Change the required fields and click Save.
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.
IMPORTANTDeletion is permanent and cannot be undone. Agents already using this MCP Server will fail on subsequent calls.
The table below covers all fields in the creation and edit forms, except the MCP configs section documented in the next section.
Field | Type | Required | Rules |
|---|---|---|---|
| MCP server client ID | Text | Yes | Minimum 1 character. Client ID used to get the access token client_credentials so the MCP Server can access the API. |
| MCP server client secret | Text (sensitive, password) | Yes | Minimum 1 character. Displayed as a password field. Client Secret used to get the access token client_credentials so the MCP Server can access the API. |
| OAuth token URL | Text | Yes | Minimum 1 character. OAuth token endpoint URL used to get the access token client_credentials so the MCP Server can access the API. |
| 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 access token. Select zero or more scopes. An empty list means any authenticated token can invoke the MCP Server. |
Field | Type | Required | Rules |
|---|---|---|---|
| API | Searchable select | Yes | Lists the APIs available in the Sensedia Platform multigateway catalog. You cannot enter arbitrary values. The displayed set depends on the previously configured Connections. Only APIs from gateways reachable through those connections appear. |
| Revision | Select | Yes | Lists the revisions of the selected API, also populated by the Sensedia Platform multigateway catalog. Disabled until you choose an API. |
| API base URL | Text | Yes | Base URL of the target API, where the gateway forwards MCP agent calls. |
| Exposed endpoint | Text | Yes | Public path the gateway exposes to the MCP Client. |
This list is required and must have 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 DATAInside each Config, at least one of Methods, Tags, and Endpoint regex must be filled in.
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 API endpoint verbs should be exposed in the MCP Server. |
| Tags | List of tags | Conditional: individually optional; required if Methods and Endpoint regex are empty | List of OpenAPI tags from the API whose endpoints should be 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 matched against the API endpoint path. Minimum 1 character when provided. |
| Type | Select (enum) | No | Values: Tool, Resource, Resource template, Exclude. When empty, the gateway assumes TOOL. |
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 parameterized resource (template URI). |
| Exclude | The endpoint is not exposed to the agent. This is useful for removing specific items when the filter includes a broad set, such as including everything from a tag except one endpoint. |
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more