---
title: "Revoke Team Binding"
method: POST
path: "/v1/teams/{team_id}/mcp/bindings/{binding_id}/revoke"
tags: ["mcp-access"]
---

# Revoke Team Binding

`POST /v1/teams/{team_id}/mcp/bindings/{binding_id}/revoke`

## Request

- Base URL: `https://api.pioneer.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.pioneer.ai/v1/teams/{team_id}/mcp/bindings/{binding_id}/revoke`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer
- TypeScript: <https://skmtc.dev/pioneer/apis/brain-api/docs/v1/teams/:team_id/mcp/bindings/:binding_id/revoke/post.ts> (a function with typed inputs; its response is checked against the schema)

Revoke a binding (requesting member or a ``MANAGE_TEAM`` human).

## Path parameters

- `team_id` string, required
- `binding_id` string, required

## Response `200`

Successful Response

- MCPBindingInfo: A single MCP client binding, pending or active.
  - `id` string, required
  - `client_id` string, required
  - `client_name` string, required
  - `requested_by` string, required
  - `confirmed_by` string, nullable, required
  - `status` 'pending' | 'confirmed' | 'revoked', required: Lifecycle of an MCP client binding (ENG-7326, E2). A binding is created ``PENDING`` when a client first reaches a team's MCP endpoint, becomes ``CONFIRMED`` once a human grants it, and ``REVOKED`` when access is withdrawn.
  - `created_at` string, date-time, required

## Other responses

- `422`: Validation Error

## Changes

- **2026-09-24** `0e5e86e2bae5`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/pioneer/apis/brain-api/changes/v1/teams/:team_id/mcp/bindings/:binding_id/revoke/post.md)

---

[API](https://skmtc.dev/pioneer/apis/brain-api.md) - [All operations](https://skmtc.dev/pioneer/apis/brain-api/llms.txt) - [OpenAPI document](https://skmtc.dev/pioneer/apis/brain-api/revisions/0e5e86e2bae5?raw)