disconnect_connector
Disconnect a project's installation of one connector — the connector withdraws it, the credentials are wiped, the row stays. Destructive.
Detaches a project's live installation of one connector. The connector withdraws the installation on its platform, the credentials are wiped and the installation turns disconnected. Members keep the access they hold; grants, resources, plans and identities are untouched; the creator can connect it again from the dashboard. An installation already disconnected is left alone. The REST twin is DELETE /v1/projects/{project}/connectors/{key}/installation.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it.
Arguments
project_id*stringUUID of the project.
connector*stringThe connector key, as `list_connectors` returns it.
What it returns
{ "data": { "installation_id": "3b8f0c6e-2d41-4a97-9e5f-1c7d6b2a8e40", "connector": "telegram", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "disconnected": true }, "meta": {}}How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-connector:delete.
RESOURCE_NOT_FOUNDthe project is not visible to this token, or context.reason is unknown_connector.
CONNECTOR_NOT_INSTALLEDthe project has no installation of the connector.
How is this guide?
Last updated on