Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
Query privacy-first web analytics — visitors, pages, referrers, goals, funnels.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Savri MCP server connects Savri's cookieless web analytics to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 15 tools: nine read visitors, pageviews, top pages, referrers, countries, goals and funnels — and six create or delete the goals, funnels and event properties those numbers are measured against. Sign-in is OAuth 2.0 with PKCE.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
savri_delete_site. We could not determine which is current.No. Anthropic's directory description says the connector reads traffic data, but the same entry lists savri_create_property, savri_delete_property, savri_create_goal, savri_delete_goal, savri_create_funnel and savri_delete_funnel. Savri's own docs group its connector tools under a read scope and a write scope, and its developer table describes the remote connector as read/write. Treat it as read-write.
Yes, according to Savri. Its Claude connector page describes savri_delete_goal as deleting a conversion goal and its completion history, and savri_delete_property as deleting an event property and its stored values. Both are one-step tool calls with no documented undo, so an agent that deletes a goal removes the measurement definition and the numbers behind it together.
OAuth 2.0 with PKCE, and no API key. We read Savri's authorization-server metadata on 2026-09-09: it requires the S256 code challenge method and publishes read and write as its supported scopes. Savri documents an access token that lasts one hour, a refresh token that lasts 30 days, and refresh-token rotation on every use.
No, according to Savri. Its documentation states the connector inherits your own site permissions, so a team member on one site sees only that site and not sites owned by other users. Savri's privacy policy repeats this, describing the grant as the same access you would have logged in yourself. We could not verify the behaviour without credentials.
Anthropic's directory lists 15 and Savri's own connector page lists 19, which it describes as 18. The four names on Savri's page but not in the directory are savri_get_property_breakdown, savri_create_site, savri_rename_site and savri_delete_site. The endpoint returned 401 to our anonymous request, so we read no live tool list and cannot settle the count.
Savri does not gate the connector itself, but it gates features the tools reach. Its documentation states funnels require the Growth plan or higher, and that API access and API keys do too. Site counts are capped per plan: 2 on Starter, 5 on Basic, 10 on Growth and 15 on Business, from $9 per month.
Aggregated statistics for 24 months and raw data for 90 days, per Savri's documentation. Its privacy policy adds that analytics data is kept while the account is active and permanently deleted within 30 days of account deletion. So a query about traffic beyond two years has no aggregated data left to read.
Two ways, both documented by Savri. Disconnect it in claude.ai under Settings then Connectors, which Savri says triggers Anthropic calling its revocation endpoint so tokens are revoked immediately. Or revoke every active token yourself from the API keys view in Savri's settings. Savri states tokens cannot be used after revocation.
llms-full.txt (fetched 2026-09-09; plan gates, pricing, retention, funnel and goal behaviour, public API periods, @savri/mcp npm package) · retrieved 2026-09-09llms.txt (fetched 2026-09-09) · retrieved 2026-09-09https://savri.io/api/mcp — HTTP 401 with a WWW-Authenticate: Bearer challenge naming resource_metadata (2026-09-09). No tool list read. · retrieved 2026-09-09scopes_supported: ["read","write"]) · retrieved 2026-09-09robots.txt (fetched 2026-09-09; Allow: / for all agents including ClaudeBot and GPTBot, with /api/ disallowed) · retrieved 2026-09-09Connect Savri once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.