Get MCP settings for an integration.
Returns the integration's MCP server configuration: whether it is `enabled`, which integration `configId` backs production calls, the `exposedToolIds` list that filters which tools the MCP server advertises, and the `apiKeyId` used to authenticate inbound JSON-RPC traffic. If no MCP config exists for the integration one is created lazily with defaults, so this endpoint is safe to call before any configuration step.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/mcp"{
"integrationId": "string",
"enabled": false,
"configId": "00000000-0000-0000-0000-000000000000",
"exposedToolIds": [
"string"
],
"description": "string",
"apiKeyId": "00000000-0000-0000-0000-000000000000",
"callUrl": "string",
"testUrl": "string",
"createdAt": 0,
"modifiedAt": 0,
"keyPrefix": "string",
"apiKey": "string"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Verifies that the provided auth configuration can successfully connect to the integration.
Only supported for auth methods with `ConfigTestSupported = true`. Returns 400 if the auth method does not support verification.
MCP JSON-RPC endpoint (production)
Single JSON-RPC entry point that external MCP clients connect to in production. Dispatches the standard MCP methods (`initialize`, `tools/list`, `tools/call`, etc.); `tools/list` reflects the integration's `exposedToolIds`, and `tools/call` resolves the integration's published `configId` revision to authenticate against the real upstream API. Authenticated via API key (the `apiKeyId` configured on the MCP settings) and concurrency-rate-limited. Use `/integrations/{integration}/mcp:test` for the sandbox equivalent that routes through the integration simulator.