Tally by Outpost
Read-only web and revenue analytics over MCP for AI assistants and their users
Answered our latest tool-list check 2 hours ago with 16 tools. It will be marked verified after 3 successful checks in 7 days.
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 0.1.1
- Listing updated
- today
Similar MCP servers
About Tally by Outpost
Tally by Outpost is an MCP server for analytics and data. It runs as a hosted remote server, so there is nothing to install locally.
The Tally MCP server lets an AI assistant query a site's analytics directly, using the same read-only API key that the REST API uses. The docs say the assistant can ask about visitors, traffic sources, pages, goals, funnels and payments, and that each tool only reads data. Connection is over Streamable HTTP with a Bearer key sent in the Authorization header.
The tool set covers overview and period comparisons, breakdowns by dimension, sales and receipts that link payments back to visits, visitor journeys, realtime activity, funnels, customer lifetime value, peak hours, and engagement. Revenue-related tools only return data when payments are connected to the site, and the docs describe a coverage view that lists unattributed revenue along with fix suggestions.
It suits people who already run their analytics in Tally and want to query it from Claude or another MCP-compatible client. Plan access is governed by the account: keys the plan does not cover receive a 402 response, and rate limits return 429.
Install
Run in a terminal
claude mcp add --transport http tally https://tallybyoutpost.com/mcpAdd to Settings → Connectors → Add custom connector
https://tallybyoutpost.com/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tally": {
"url": "https://tallybyoutpost.com/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tally": {
"type": "http",
"url": "https://tallybyoutpost.com/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tally": {
"serverUrl": "https://tallybyoutpost.com/mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://tallybyoutpost.com/mcpEnter a Name (for example "Tally by Outpost"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tally": {
"type": "http",
"url": "https://tallybyoutpost.com/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (16)
Read directly from the server.
All 16 tools say they're read-only.
From the server's own tool annotations; not verified by us.
- list_sitesSays read-only
- The site this API key reads: its id, name, domain, time zone and how visitors are counted (cookie, cookieless or consent).
- get_overviewSays read-only
- Visitors, pageviews, visits, median engaged time and, when payments are connected, net revenue, sales, refunds, conversion rate and revenue per visitor, for a period and the window before it, with the change between them. Also the visitors live now.
- get_breakdownSays read-only
- The top values of one dimension (source, channel, page, country, device, campaign …) by distinct visitors, or by revenue, each with its share of visitors and the revenue its visitors brought.
- compare_periodsSays read-only
- A period against the window just before it (previous) or the same dates a year earlier (year): every overview number for both, and the relative change. Changes are null where the site's records don't reach back far enough to compare.
- list_salesSays read-only
- Payments newest first, each with its amount as charged and in US dollars, whether it is linked to a visitor, how (method and confidence), and why not when it isn't. Filter to unlinked payments or refunds.
- get_receiptSays read-only
- One payment's receipt: the evidence chain that ties it to a visit (first visit, visits before paying, the credited visit, the handle that matched and where), every provider id, and the payment it follows from.
- get_coverageSays read-only
- How much of the period's revenue is attributed to a visitor, by method, and the fix-it list for what isn't (with code to paste).
- list_visitorsSays read-only
- Visitors (visits on a cookieless site) of a period, most recent first or by revenue or likely to buy, with visits, pages, engaged time per visit, revenue and their latest visit.
- get_visitorSays read-only
- One visitor's whole journey: every visit with its pages, engaged time, goals and outbound clicks, their payments, first touch and the touch credited with the sale.
- get_realtimeSays read-only
- Who is on the site in the last five minutes (page, place, source, device) and the sales of the last hour.
- get_goalsSays read-only
- Every goal completed in the period with completions, converting visitors, conversion rate and the revenue of converting visitors; give `goal` for one goal's properties. Lists the site's funnels.
- get_funnelsSays read-only
- The site's funnels with each step's visitors, conversion from the step before and from the first, and drop-off; or one funnel with `funnel`.
- get_customer_valueSays read-only
- Lifetime value by the source that first brought each customer: customers, revenue, average per customer, renewals and repeat rate, over every payment on record.
- get_peak_hoursSays read-only
- Visits, sales and revenue by weekday and hour in the site's time zone, and the busiest three hours when the data is enough to say.
- get_engagementSays read-only
- How pages are read: views, median reading time, average scroll depth and the share read to the end, per page and overall, and the common entry and exit pages.
- get_purchase_pathsSays read-only
- How buyers got there: time from first visit to purchase, visits and pages before paying, first-touch to credited-source flows, and the pages buyers saw before paying.
What it does
- Read-only analytics tools
- Every exposed tool only reads data, so an assistant can query figures without changing the site.
- Revenue linked to visits
- Sales tools show whether each payment is tied to a visitor, with the method, confidence and evidence chain.
- Funnels and goals
- Goal completions, funnel step conversion and drop-off can be pulled for a chosen period.
- Visitor journey lookup
- A single visitor's visits, pages, goals, payments and first and credited touch can be retrieved.
- Standard MCP transport
- Works over Streamable HTTP with JSON-RPC 2.0 and several protocol revisions, using a plain header for the key.
Good for
- Asking an assistant which traffic sources produced the most revenue this month
- Checking funnel drop-off between pages without opening the dashboard
- Investigating why a specific payment is not linked to a visit
- Reviewing customer lifetime value by acquisition source
- Reading realtime visitors and recent sales during a campaign
Tally by Outpost FAQ
How does an assistant connect to the server?
The docs give the address https://tallybyoutpost.com/mcp and say to send the REST API key as an Authorization Bearer header. They include an example command for Claude Code.
Can the MCP tools change any data?
No. The docs state that every tool only reads.
Which protocol versions are supported?
The docs say Streamable HTTP with JSON-RPC 2.0 on revision 2026-07-28, and that clients of 2025-11-25, 2025-06-18 and 2025-03-26 are also served.
What happens if my plan does not cover a key?
The docs say a key the account's plan doesn't cover gets a 402 response, and rate-limited calls get 429 with Retry-After, as over REST.
How do I add Tally by Outpost to Claude Code?
Run this command in your terminal: claude mcp add --transport http tally https://tallybyoutpost.com/mcp
What are the best alternatives to Tally by Outpost?
The closest alternatives to Tally by Outpost are SuprAnalytics, Tagely Analytics, Wholetally, Tally and Web Analytics.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 19 November 2026.
- Install steps: from the official MCP Registry entry.