SnozeDevelopers
API referenceIntegrations

Call a tool on a remote MCP connection

Invokes one tool on the connection's remote MCP server with the supplied arguments and returns its result. Requires the `integrations:write` workspace permission and an explicit `confirmed: true` in the body, because the call runs against the third-party system; a tool outside the connection's allowlist is refused. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.

POST
/v1/workspaces/{workspaceId}/integrations/connections/{connectionId}/mcp/tools/call

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
connectionId*string

Request Body

application/json
  1. body
name*string
arguments?|null
confirmed*true
Value intrue

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X POST 'https://api.snoze.dev/v1/workspaces/string/integrations/connections/string/mcp/tools/call' \  -H 'Content-Type: application/json' \  -d '{  "name": "string",  "confirmed": true}'
Example Response
{  "data": {    "tool": "string",    "result": {}  }}

List the tools exposed by a remote MCP connection

Queries the connection's remote MCP server for its tool list and returns the tools with their input schemas, filtered by the allowlist stored on the connection. Requires the `integrations:read` workspace permission; a server that cannot be reached or that answers with an error surfaces as a remote MCP failure.

Preview what deleting a connection would remove

Reports what disconnecting would affect — the connector-owned databases, mirrored resources, and placements that depend on the connection — so the consequences can be shown before the delete. Read-only, but gated on the `integrations:write` workspace permission because only a caller who could perform the delete may see the preview.