Custom connectors

Turn a remote MCP connector tool off or on

status: "disabled" switches the tool off for every connection, "active" turns it back on; nothing else is accepted (400). A tool's tier is always the server's label and cannot be set here. Needs the connector's own edit access (ownership or an edit share) on an org's own connector, connector:manage on one Elaichi publishes. The 200 is the tool with its whole definition (description, input_schema, output_schema, annotations, derived_tier). Recorded in the audit log as connector.tool_updated with the status before and after.

patch/connector/{slug}/tool/{name}

Request

  • Base URL: https://api.elaichi.ai
  • URL: https://api.elaichi.ai/connector/{slug}/tool/{name}
  • Auth: HTTP bearer

Path parameters

slugstring required

Connector slug of a remote MCP connector.

namestring required

The tool's Elaichi name, as GET /connector/{slug}/tool returns it.

Headers

X-Organization-Idstring

Target organization (org_…). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.

Request body

status'active' | 'disabled' required

Response

OK

object required

Changes

No recorded changes to this operation across all 1 revision of this API.