How often AI clients called the project's MCP server tools, and how many distinct clients called them.
GET/v1/projects/{projectId}/addons/mcp_server/usageTry it
Session token
Returns how many tool calls the project's MCP server answered in the window, how many distinct clients made them, and the calls per tool.
Note
Session JWT and org membership required. Any role can read it — an API key gets 401, a non-member 403.
Any plan. Usage stays readable after a downgrade or with the MCP Server add-on switched off.
Path Parameters
NameDescription
projectId:stringpathRequired
The project ID.
Query Parameters
NameDescription
days:integerquery
Time window in days, 1–90.
Default7
Response Fields
NameDescription
data.toolCalls:integer
Tool calls in the window, successful or not.
data.clients:integer
Distinct clients. Clients are counted without storing their IP addresses.
data.byTool:array
Calls per tool, most called first, at most 50 tools.
What is counted
Every tools/call request to the project's MCP endpoint — the doc-site endpoint at /_mcp, served by /v1/projects/{projectId}/mcp — from anonymous readers and from readers signed in to a private site alike. Listing tools is not a call, and neither is a request refused because it wasn't signed in. The account-level hosted connector at https://api.syntext.dev/mcp and the local @syntext/mcp package are not counted here.