Test an MCP server

Connect to the MCP server from the platform and list its tools, with the stored headers. Use it after adding a server, and to see the exact tool names for allowed_tools.

To test a token you only pass per call, send it in headers: those are merged over the stored headers for this test only and are not stored.

Authorization

BearerAuth

AuthorizationBearer <token>

API key authentication. Get your key from the dashboard.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

headers?

Header names and values sent with every request to the MCP server, typically an API key or a bearer token that you obtained from the server's provider. At most 10 headers. A name is an HTTP token; Host, Content-Type, Content-Length, Transfer-Encoding, Connection, Accept, Accept-Encoding, Mcp-Session-Id, Mcp-Protocol-Version and Last-Event-Id are set by the platform and cannot be set here. A value is a non-empty string of at most 8192 characters without line breaks.

Propertiesproperties <= 10

Response Body

`application/json`

curl -X POST "https://example.com/mcp-servers/497f6eca-6276-4993-bfeb-53cbbbba6f08/test" \  -H "Content-Type: application/json" \  -d '{}'

{
  "ok": true,
  "duration_ms": 412,
  "tools": [
    {
      "name": "search_mail",
      "description": "Search the mailbox for messages that match a query",
      "input_schema": {}
    }
  ],
  "error": "The server answered HTTP 401: check the headers of this MCP server."
}

{
  "error": "Invalid API key",
  "message": "string"
}

{
  "error": "Invalid API key",
  "message": "string"
}

{
  "error": "Invalid API key",
  "message": "string"
}

Test an MCP server

Authorization

Path Parameters

Request Body

Response Body

200application/json

400application/json

401application/json

404application/json

`application/json`

`application/json`

`application/json`

`application/json`