---
title: "List Team Bindings"
method: GET
path: "/teams/{team_id}/mcp/bindings"
tags: ["mcp-access"]
---

# List Team Bindings

`GET /teams/{team_id}/mcp/bindings`

List pending and active MCP client bindings for the team.

## Path parameters

- `team_id` string, required

## Response `200`

Successful Response

- ListMCPBindingsResponse — Pending and active bindings for a team.
  - `pending` MCPBindingInfo[], required
    - `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
  - `active` MCPBindingInfo[], required
    - `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** `1cffaad2a921` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/pioneer/apis/brain-api/changes/teams/:team_id/mcp/bindings/get.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/1cffaad2a921?raw)