What is the key difference between Callrail MCP and Token Meter?

Callrail MCP belongs to the Marketing category with local stdio execution, while Token Meter belongs to the Marketing category with local stdio execution.

How do I install Callrail MCP or Token Meter in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Callrail MCP and Token Meter free or paid?

Callrail MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Token Meter operates under a Freemium model (No auth required).

Which MCP server has more tools and community activity?

Callrail MCP lists 40 tools with 2 views and 2 GitHub stars. Token Meter lists 4 tools with 3 views and 1 GitHub stars.

Can I use both Callrail MCP and Token Meter together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Callrail MCP vs Token Meter

In-depth architectural comparison of the Callrail MCP and Token Meter MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Callrail MCP

Marketing · Local stdio

Quality: 60/100 (Good) | Auth: API Key required

Token Meter

Marketing · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Verdict Summary: Choose Callrail MCP if you need specialized Marketing tools running via a local process. Choose Token Meter if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Callrail MCP when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: CALLRAIL_API_KEY, CALLRAIL_API_KEY_FILE.
Primary tools included: list_accounts, list_companies, list_trackers.

Explore Callrail MCP Details

Choose Token Meter when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: usage_summary, recent_sessions, session_tools.

Explore Token Meter Details

Feature & Specification Comparison

Specification	Callrail MCP pghdma Marketing	Token Meter whdrnr2583-cmd Marketing
Summary	CallRail REST API v3 integration with 49 tools for call tracking, form submissions, transcripts, full CRUD on tags/trackers/companies/users, plus agency-specific aggregation tools (usagesummary for per-client cost attribution, compareperiods for MoM deltas, bulkupdatecalls with dry-run, spamdetector, calleligibilitycheck for Google Ads conversion debugging). Built by an actual CallRail customer for agency use. Install: pipx install callrail-mcp.	Local-first dashboard + MCP server for Claude Code and Codex token usage. Cost, per-MCP/per-tool breakdown, hourly distribution, and session drill-down — your data never leaves your machine.
Category & Scope

Tools & Capabilities Breakdown

Callrail MCP Tools (40)

list_accounts

List accessible CallRail accounts

list_companies

List companies (clients) under an account. Optional `status="active"` filter and `page

list_trackers

List tracking phone numbers and their source mapping. Optional `status="active"` filter

get_tracker

Full detail for one tracker

list_calls

Paginated call list. Filter by company, date, and `answer_status

get_call

Full detail for a specific call

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Callrail MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pghdma-callrail-mcp": {
      "command": "uvx",
      "args": [
        "callrail-mcp"
      ],
      "env": {
        "CALLRAIL_API_KEY": "YOUR_CALLRAIL_API_KEY_HERE",
        "CALLRAIL_API_KEY_FILE": "YOUR_CALLRAIL_API_KEY_FILE_HERE"
      }
    }
  }
}

Token Meter Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "whdrnr2583-cmd-token-meter": {
      "command": "npx",
      "args": [
        "-y",
        "@whdrnr2583/token-meter"
      ]
    }
  }
}

Frequently Asked Questions

Callrail MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Token Meter belongs to Marketing using local stdio subprocess. Select Callrail MCP when you need capabilities focused on marketing and Token Meter when you require tools for marketing.

More alternatives to Callrail MCP More alternatives to Token Meter Marketing category hub