Uninstall a plugin

Removes one installation of a plugin: mcp_server_id (or connection_id for a native connector) names it, or scope picks the caller’s personal one or the workspace’s (reason_id with scope=reason a Reason’s). With exactly one manageable installation neither is needed; with several it answers 409 listing them. Removing an MCP installation revokes its OAuth grant at the provider where supported and records connection.removed. Its bundled skills installed in the same scope are removed too unless keep_skills=true, or another installation of the plugin still uses them (an installation in the same scope, or the workspace’s shared skills for a legacy personal or Reason installation). Requires managing the installation (installation-policy: owners and admins, or the member who installed a personal one).

_{Scope: mcp:write}

DELETE /v3/organizations/{orgId}/plugins/{slug}

Uninstall a plugin

cURL

curl --request DELETE \
  --url https://api.reasonmachines.com/v3/organizations/{orgId}/plugins/{slug} \
  --header 'Authorization: Bearer <token>'

200

{
  "ok": true,
  "removed": [
    {
      "connection_id": "<string>",
      "adapter": "mcp",
      "scope": "personal"
    }
  ],
  "removed_skills": [
    "<string>"
  ],
  "plugin": {
    "slug": "<string>",
    "name": "<string>",
    "description": "<string>",
    "icon": "<string>",
    "source": "curated",
    "auth_type": "none",
    "secret_names": [
      "<string>"
    ],
    "scope": "personal",
    "supported_scopes": [
      "personal"
    ],
    "connectable": true,
    "setup": {
      "code": "<string>",
      "owner": "<string>",
      "message": "<string>"
    },
    "docs_url": "<string>",
    "website_url": "<string>",
    "verified": true,
    "bundled_skills": [
      {
        "slug": "<string>",
        "name": "<string>",
        "description": "<string>",
        "installed": true,
        "installed_scopes": [
          "personal"
        ]
      }
    ],
    "installed": true,
    "mcp_server_id": "<string>",
    "connection_state": "<string>",
    "connection_checked_at": "<string>",
    "accounts": [
      {
        "connection_id": "<string>",
        "adapter": "mcp",
        "mcp_server_id": "<string>",
        "scope": "personal",
        "reason_id": "<string>",
        "account_id": "<string>",
        "account_name": "<string>",
        "connection_state": "<string>",
        "connection_checked_at": "<string>",
        "connection_error_code": "<string>",
        "enabled": true,
        "can_manage": true,
        "reason_mode": "member"
      }
    ]
  }
}

Authorizations

Authorization · string · header · required

Your Reason API key from Settings › API keys. New keys use reason_; legacy ara_ keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, devices:read, devices:write, devices:use, computers:read, computers:write, ssh:write, knowledge:read, memory:read, memory:write, skills:read, skills:write, pages:read, pages:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, network:read, network:write, automations:read, automations:write, agent_auth:read. devices:write, devices:use, computers:read, computers:write, ssh:write, network:read and network:write are opt-in, excluded from default keys. computers:read lists visible cloud and connected computers without waking them or granting execution access. devices:read discovers local Device targets; devices:use separately consents to local execution, so a discover-and-run local workflow needs both. devices:write manages enrollment and device grants; computers:write creates or deletes cloud computers; ssh:write manages retained SSH access. network:read reads the saved workspace network policy; network:write replaces custom allowed hosts and requires a current organization owner/admin. Legacy project PATCH requests containing network_allowed_hosts also require network:write plus their existing run scope and project management permission; saved project hosts do not affect current session egress. Only owners/admins can mint or manage keys with network:write; keys cannot grant themselves more authority. See /docs/network-policies for replacement semantics and runtime applicability. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:read reads sessions, including the assistant, reasoning and tool activity in their events. sessions:debug is privileged: only for organization owners/admins, it expands session events to the full diagnostic projection (diagnostic event kinds, status text and raw event metadata).

Scopes

mcp:write

Path Parameters

orgId · string · required

Organization id or slug. Resolve it with GET /v3/self.

slug · string · required

Plugin slug from listPlugins, stable across installs and uninstalls.

Required string length: 1 - 120

Query Parameters

mcp_server_id · string<uuid>

The MCP installation to remove (from accounts).

connection_id · string<uuid>

The native connector connection to remove (from accounts).

scope · enum<string>

Remove the installation in this scope.

Available options: personal, organization, reason

reason_id · string<uuid>

Also list this Reason's own installations in accounts (requires access to the Reason).

keep_skills · enum<string>

true keeps the bundled skills installed.

Available options: true, false

Response

200

application/json

Removed.

ok · boolean · required

removed · object[] · required

Installations removed. OAuth grants are revoked at the provider where it supports revocation.

Show child attributes

removed_skills · string[] · required

Bundled skill slugs removed; empty with keep_skills=true.

plugin · object · required

Show child attributes