In-depth architectural comparison of the Callrail MCP and Google Tag Manager MCP Server 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
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Callrail MCP if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server 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.
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.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
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 is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Callrail MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.
Popular comparisons with Google Tag Manager MCP Server
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.