Wholetally

com.wholetallyPublished by wholetally.comOfficial publisherv1.0.0Updated Nov 11, 2026

Cookieless analytics for agents: visitors, pages, sources, AI crawlers, funnels and revenue.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote, OAuth-protected analytics server that lets an assistant query cookieless website metrics such as visitors, pages, sources, AI crawlers, funnels and…

What you can do
  • Query cookieless web analytics data for a site.
  • Review visitor, page and traffic-source metrics.
  • Inspect AI crawler activity.
  • Examine funnel and revenue figures.
  • No tool list is published, so exact operations are not documented in the supplied material.
When to use it
Useful when you want an assistant to pull website traffic, funnel or revenue numbers from Wholetally while answering questions or drafting reports, without exporting data by hand.
Requirements
A remote endpoint at api.wholetally.com reached over streamable HTTP, plus an OAuth sign-in to a Wholetally account. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Wholetally analytics account, so the assistant can read whatever that account can see; review the scopes granted. The published material does not state whether any tools write or change data.

Installation

In SourceWeft

  1. Open Wholetally in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.wholetally%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wholetally": {
      "type": "http",
      "url": "https://api.wholetally.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 11, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.