SnozeDevelopers
API referenceIntegrations

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.

GET
/v1/workspaces/{workspaceId}/integrations/connections/{connectionId}/mcp/tools

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

Response Body

Success

application/json
  1. response
data*array<>
Example Request
curl -X GET 'https://api.snoze.dev/v1/workspaces/string/integrations/connections/string/mcp/tools'
Example Response
{  "data": [    {      "name": "string",      "title": "string",      "description": "string",      "inputSchema": {}    }  ]}

Update the sync state of one provider object type

Enables or disables a single provider object type on a connection and replaces its field mappings, returning the refreshed connection detail. Requires the `integrations:write` workspace permission. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.

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.