# Read workspace mcp usage

What the models connected to this workspace have been doing: which MCP tools, from which clients, driven by which person or which key, folded per day, with the failures. `tool` narrows inside MCP traffic rather than matching any route that shares the word; `key`, `client` and `class` narrow further. ADMIN ONLY and deliberately NOT plan-gated — a workspace whose Workspace API tier lapsed still needs to see what its models did while it had one. What the PEOPLE did is /v1/workspace/usage/summary.

Access class: `workspace:admin`.

## Endpoint

`GET /v1/workspace/mcp/usage`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "answer": {
      "filters": {},
      "retention": "string",
      "since": "string",
      "sink": "string",
      "total": 1.5,
      "truncated": true
    },
    "callers": [
      "string"
    ],
    "clients": [
      "string"
    ],
    "failures": [
      "string"
    ],
    "perDay": [
      "string"
    ],
    "tools": [
      "string"
    ]
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```