---
title: "Turn a remote MCP connector tool off or on"
method: PATCH
path: "/connector/{slug}/tool/{name}"
tags: ["Custom connectors"]
---

# Turn a remote MCP connector tool off or on

`PATCH /connector/{slug}/tool/{name}`

## Request

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

`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.

## Path parameters

- `slug` string, required
- `name` string, required

## Headers

- `X-Organization-Id` string

## Request body

- object
  - `status` 'active' | 'disabled', required

## Response `200`

OK

- object

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `429`: Rate limited

---

[API](https://skmtc.dev/elaichi/apis/elaichi-api.md) · [All operations](https://skmtc.dev/elaichi/apis/elaichi-api/llms.txt) · [OpenAPI document](https://skmtc.dev/elaichi/apis/elaichi-api/revisions/b22cfb7b6d15?raw)