Telemetry
Telemetry is required only on the hosted Free plan at mcp.getautomata.app. A self-hosted deployment never sends us tool calls, reasons, usage, or anything else, and never requires telemetry. It is off by default. If an administrator chooses to turn it on, the records stay in that deployment's own database and nowhere else.
Telemetry is a 30-day history of the tool calls made with your connector tokens, with the one-line reason the AI client gave for each. It lets an organization see what its connectors are actually used for.
Who it applies to
| Where Automata runs | Telemetry | Where records are stored |
|---|---|---|
| Hosted, Free plan | Always on; cannot be turned off | The hosted service's database |
| Hosted, Pro plan | Off by default; an administrator can turn it on | The hosted service's database |
| Self-hosted | Off by default; an administrator can turn it on | Your own database only. Nothing is sent to us |
Moving a hosted organization from Free to Pro hands the choice back to its administrators, and telemetry goes back to off unless an administrator turned it on.
What is recorded
While telemetry is on, each tool call is stored with:
- the tool's name, for example
search-messages; - whether the call worked;
- the reason the AI client gave, clipped to 300 characters, or nothing if it gave none;
- the client's user agent;
- the connector token it was made with, and when.
Tool arguments, results, message content, and query rows are never recorded.
The reason argument
Every tool takes an optional reason argument: one sentence from the model on why it is making the call, for example "User asked to find invoices from a vendor received last week and total them." MCP never sends the user's prompt to the server, so this is the closest an organization can get to knowing what its connectors are used for. It is the model's own account, not the prompt.
Automata removes reason before the tool runs, so it never changes what a tool does. With telemetry off, it is discarded.
Who can see it
Click a connector token's Last used date to see its calls, newest first.
- A member sees the calls made with their own tokens.
- An administrator sees the calls made with every token in the organization.
Everyone in the organization can see on the Team page whether telemetry is on, because their calls are recorded too.
What it is never used for
A reason can mention what someone asked about, and a prompt-injected message can make the model write anything there. So reasons are:
- kept only in the app database, and shown as plain text;
- never written to logs, analytics, or account events;
- never returned to an AI client over MCP;
- never used for access decisions, limits, or billing.
Turning it on or off
An administrator changes it on the Team page under Telemetry. On the hosted Free plan the box is locked on; upgrade to Pro to turn it off.
Turning it off stops collection immediately. Calls already stored are deleted when their 30 days are up.
Related
- See which clients use a token lists the MCP clients that connected with each token. It is separate from telemetry and always on.
- Privacy Policy covers how the hosted service handles this data.