Get MCP connection

Overview

An MCP connection gives your agents the tools on a remote MCP server that speaks Streamable HTTP. Store the server URL and its credentials once, then attach the connection to any agent in your tenant. Credentials are never returned. Connections have no userId. Servers that sign in with OAuth finish connecting in the dashboard.

Endpoints

List MCP connectionsGET/v1/mcp-connections

List MCP connections.

Lists your tenant's MCP connections, sorted by name. Credentials are never returned.

Request

Requires bearer authentication.

There are no parameters and no request body.

Returns 200 OK as application/json. Your tenant's MCP connections.

Response schema: McpConnectionList.

{
  "mcpConnections": [
    {
      "id": "mcp_2Rk7Wm4XsQ9dHv1B",
      "name": "Docs Search",
      "url": "https://mcp.example.com/mcp",
      "authType": "bearer",
      "status": "connected",
      "credentialFragment": "x7Qa",
      "lastAuthErrorCode": null,
      "oauthIssuer": null,
      "oauthResource": null,
      "tokenExpiresAt": null,
      "createdAt": "2026-07-10T10:00:00.000Z",
      "updatedAt": "2026-07-10T10:00:00.000Z"
    }
  ]
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY"

Create MCP connectionPOST/v1/mcp-connections

Create an MCP connection.

Creates an MCP connection you can attach to any agent in your tenant. Names are unique within your tenant, and credentials are never returned. The fields you send depend on authType: bearerToken is required for bearer; clientId and clientSecret are required together for oauth_client_credentials; for oauth_authorization_code they are optional but go together. For none, bearer, and oauth_client_credentials, Blazing Agents checks the live server before saving and returns status: "connected". For oauth_authorization_code, it saves the connection as needs_auth, and an administrator finishes sign-in from the dashboard. A failed create saves nothing.

Request

Requires bearer authentication and a JSON body.

Returns 201 Created as application/json. The created MCP connection.

Response schema: McpConnection.

{
  "id": "mcp_2Rk7Wm4XsQ9dHv1B",
  "name": "Docs Search",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "status": "connected",
  "credentialFragment": "x7Qa",
  "lastAuthErrorCode": null,
  "oauthIssuer": null,
  "oauthResource": null,
  "tokenExpiresAt": null,
  "createdAt": "2026-07-10T10:00:00.000Z",
  "updatedAt": "2026-07-10T10:00:00.000Z"
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl --request POST "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"name":"Docs Search","url":"https://mcp.example.com/mcp","authType":"bearer","bearerToken":"mcp_live_4f8Kq2Lz9Xw7x7Qa"}'

Test MCP connectionPOST/v1/mcp-connections/:id/test

Test an MCP connection.

Connects to the MCP server with the stored credentials and returns its server details and tool names. The outcome is saved on the connection: success sets status to connected and clears lastAuthErrorCode; a rejected credential sets needs_auth; any other failure sets error. Server and network failures return 200 with ok: false and an error code, not an error status. Testing an OAuth connection can refresh its stored tokens first.

Request

Requires bearer authentication.

Returns 200 OK as application/json. The test result.

Response schema: McpConnectionTest.

{
  "ok": true,
  "latencyMs": 412,
  "server": {
    "name": "docs-search",
    "version": "1.4.0"
  },
  "toolCount": 2,
  "toolNames": [
    "search_docs",
    "get_page"
  ]
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl --request POST "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections/mcp_1234567890ABCDEF/test" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY"

Reconnect MCP connectionPOST/v1/mcp-connections/:id/reconnect

Reconnect an MCP connection.

Replaces an MCP connection's server URL and credentials. The fields you send depend on authType, as when you create a connection: bearerToken is required for bearer; clientId and clientSecret are required together for oauth_client_credentials; for oauth_authorization_code they are optional but go together. For none, bearer, and oauth_client_credentials, Blazing Agents checks the live server before replacing anything and returns status: "connected"; a failed check leaves the existing configuration as it was. For oauth_authorization_code, it saves the replacement as needs_auth, and an administrator finishes sign-in from the dashboard.

Request

Requires bearer authentication and a JSON body.

Returns 200 OK as application/json. The reconnected MCP connection.

Response schema: McpConnectionReconnectResult.

{
  "status": "connected",
  "connection": {
    "id": "mcp_2Rk7Wm4XsQ9dHv1B",
    "name": "Docs Search",
    "url": "https://mcp.example.com/mcp",
    "authType": "bearer",
    "status": "connected",
    "credentialFragment": "8Rw2",
    "lastAuthErrorCode": null,
    "oauthIssuer": null,
    "oauthResource": null,
    "tokenExpiresAt": null,
    "createdAt": "2026-07-10T10:00:00.000Z",
    "updatedAt": "2026-07-10T10:20:00.000Z"
  }
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl --request POST "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections/mcp_1234567890ABCDEF/reconnect" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"authType":"bearer","url":"https://mcp.example.com/mcp","bearerToken":"mcp_live_9Tb3Vc6Nm1Pq8Rw2"}'

Get MCP connectionGET/v1/mcp-connections/:id

Get an MCP connection.

Retrieves one MCP connection, including its current status. Credentials are never returned.

Request

Requires bearer authentication.

Returns 200 OK as application/json. The MCP connection.

Response schema: McpConnection.

{
  "id": "mcp_2Rk7Wm4XsQ9dHv1B",
  "name": "Docs Search",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "status": "connected",
  "credentialFragment": "x7Qa",
  "lastAuthErrorCode": null,
  "oauthIssuer": null,
  "oauthResource": null,
  "tokenExpiresAt": null,
  "createdAt": "2026-07-10T10:00:00.000Z",
  "updatedAt": "2026-07-10T10:00:00.000Z"
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections/mcp_1234567890ABCDEF" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY"

Update MCP connectionPATCH/v1/mcp-connections/:id

Update an MCP connection.

Renames an MCP connection. Send at least one field. The URL and credentials stay as they are; change them with reconnect.

Request

Requires bearer authentication and a JSON body.

Returns 200 OK as application/json. The updated MCP connection.

Response schema: McpConnection.

{
  "id": "mcp_2Rk7Wm4XsQ9dHv1B",
  "name": "Docs Search Production",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "status": "connected",
  "credentialFragment": "x7Qa",
  "lastAuthErrorCode": null,
  "oauthIssuer": null,
  "oauthResource": null,
  "tokenExpiresAt": null,
  "createdAt": "2026-07-10T10:00:00.000Z",
  "updatedAt": "2026-07-10T10:15:00.000Z"
}

Errors

See REST errors for the error envelope and shared codes.

cURL

curl --request PATCH "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections/mcp_1234567890ABCDEF" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"name":"Docs Search Production"}'

Delete MCP connectionDELETE/v1/mcp-connections/:id

Delete an MCP connection.

Deletes an MCP connection and revokes its stored OAuth credentials. Detach the connection from every agent first; a connection that is still attached cannot be deleted.

Request

Requires bearer authentication.

Returns 204 No Content. The MCP connection was deleted.

Errors

See REST errors for the error envelope and shared codes.

cURL

curl --request DELETE "$BLAZING_AGENTS_BASE_URL/v1/mcp-connections/mcp_1234567890ABCDEF" \
  --header "Authorization: Bearer $BLAZING_AGENTS_API_KEY"

Next

• MCP connections to give an agent remote tools.
• Agents API to control what each attachment forwards.