Skip to content

[Access] Document MCP analytics response-status filtering #34343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
kennyj42 wants to merge 2 commits into
base: production
Choose a base branch
from
Draft

[Access] Document MCP analytics response-status filtering #34343

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4a544d
[Access] Document MCP analytics response-status filtering
kennyj42 Oct 14, 2026
b318d1e
Empty commit to trigger worker preview
mvvmm Oct 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions src/content/changelog/access/2026-10-14-mcp-analytics-response-status.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: Filter MCP tool-call analytics by response status
description: Count successful, failed, or cached MCP tool calls separately, with successful calls as the default.
date: 2026-10-14
products:
- access
- cloudflare-one
---

MCP tool-call analytics support a `response_status` query parameter on the account, portal, and server timeseries endpoints. Use `success`, `error`, or `cached` to count one status, or `all` to include every status.

The default is `success`. Previously, counts included failed and cached calls. If you need the previous all-status counts, set `response_status=all` explicitly:

```txt
GET /accounts/{account_id}/access/ai-controls/mcp/analytics/tool-calls/timeseries?response_status=all
```

The response includes the selected `response_status`. Invalid values, including an empty value, return `400`.

For all query parameters and scoped endpoints, refer to [View tool-call analytics](/cloudflare-one/access-controls/ai-controls/mcp-portals/#view-tool-call-analytics).
17 changes: 10 additions & 7 deletions src/content/docs/cloudflare-one/access-controls/ai-controls/mcp-portals.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -700,6 +700,8 @@ The `auth_credentials` field accepts two forms:

Use the account endpoint to retrieve daily or monthly MCP tool-call counts across the account:

By default, these counts include only successful tool calls. To include errors and cached calls, set `response_status=all`. Use `error` or `cached` to count either status separately.

<CURL
url="https://api.cloudflare.com/client/v4/accounts/{account_id}/access/ai-controls/mcp/analytics/tool-calls/timeseries?granularity=daily&aggregate=false&tz=utc&days=30"
method="GET"
Expand All @@ -708,14 +710,15 @@ Use the account endpoint to retrieve daily or monthly MCP tool-call counts acros

The same query parameters apply to each endpoint:

| Parameter | Values and behavior |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `granularity` | `daily` or `monthly`. Defaults to `daily`. |
| `aggregate` | `true` or `false`. Defaults to `false`. Set to `true` to request aggregated counts. |
| `tz` | `utc`, `Z`, or a fixed `+HH:MM` or `-HH:MM` offset. Defaults to `utc`. Offsets range from `-12:00` through `+14:00`; `+14:00` and `-12:00` are the limits. The offset is used for local-day bucketing and does not account for daylight saving time changes within the window. |
| `days` | An integer from `1` to `179`. For daily results, this sets the trailing window and defaults to `7`. It is ignored when `granularity=monthly`. |
| Parameter | Values and behavior |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `granularity` | `daily` or `monthly`. Defaults to `daily`. |
| `aggregate` | `true` or `false`. Defaults to `false`. Set to `true` to request aggregated counts. |
| `tz` | `utc`, `Z`, or a fixed `+HH:MM` or `-HH:MM` offset. Defaults to `utc`. Offsets range from `-12:00` through `+14:00`; `+14:00` and `-12:00` are the limits. The offset is used for local-day bucketing and does not account for daylight saving time changes within the window. |
| `days` | An integer from `1` to `179`. For daily results, this sets the trailing window and defaults to `7`. It is ignored when `granularity=monthly`. |
| `response_status` | `success`, `error`, `cached`, or `all`. Defaults to `success`. Set to `all` to include every status. Invalid values, including an empty value, return `400`. |

The response `result` includes the selected `granularity`, `aggregate`, and `tz`, the `start` and `end` of the window as epoch milliseconds, a `series` of `day` and `count` values, and the `total` count. The window includes `start` and excludes `end`. Daily `day` values use `YYYY-MM-DD` in the requested timezone offset.
The response `result` includes the selected `granularity`, `aggregate`, `tz`, and `response_status`, the `start` and `end` of the window as epoch milliseconds, a `series` of `day` and `count` values, and the `total` count. The window includes `start` and excludes `end`. Daily `day` values use `YYYY-MM-DD` in the requested timezone offset.

Use a scoped endpoint to limit the counts:

Expand Down
Loading