MCP JSON-RPC endpoint (sandbox)
Mirrors the surface of `/integrations/{integration}/mcp:call` — same JSON-RPC methods, same API-key auth, same rate limiting — but `tools/call` requests are dispatched to the integration simulator instead of the real upstream. Use this from eval harnesses and CI to exercise an MCP client against deterministic, side-effect-free responses. The simulator still respects `exposedToolIds`, so changing what production clients can see also changes what sandbox clients can see.
API-Only Endpoint
This endpoint is available via API only and requires authentication using the X-API-KEY header.
Fill in your parameters below and the code samples will update automatically.
To generate an API key, see the Settings guide.
Authorization
ApiKey API key passed in the X-API-KEY header. Generate one from the Fruxon settings.
In: header
Path Parameters
The integration ID.
The tenant identifier
The JSON-RPC request envelope.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/mcp:test" \ -H "Content-Type: application/json" \ -d '{ "property1": {}, "property2": {} }'{
"property1": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {}
}
},
"root": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {}
},
"root": {}
}
},
"property2": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {}
}
},
"root": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {
"options": {
"propertyNameCaseInsensitive": true
},
"parent": {},
"root": {}
},
"root": {}
}
}
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Rotate the MCP key for an integration.
Mints a fresh secret with the same `mcp:invoke` scope, binds the MCP config to it, and revokes the original. The raw secret is returned once on `apiKey` — the user must update their MCP client config (Claude Desktop, Cursor) with the new value. Rotating renders any previously-distributed copy of the key permanently unusable.
Lists all skills available in the workspace, including built-in and custom skills.
Returns every skill visible to the tenant — built-in skills shipped with Fruxon plus skills the tenant has authored or imported. Use the returned skill IDs when configuring an agent's allowed skill set; agents activate skills mid-conversation by matching the user request against the skill's description.