In-depth architectural comparison of the Lead Scoring AI 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
Lead Scoring AI MCP
Marketing · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Token Meter
Marketing · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lead Scoring AI 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 Lead Scoring AI MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: B2B lead scoring, Lead engagement tracking, Lead prioritization.
Lead Scoring Ai tools for AI agents. Capabilities: score lead, add lead, update lead activit...
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.
Lead Scoring AI MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Token Meter belongs to Marketing using local stdio subprocess. Select Lead Scoring AI MCP when you need capabilities focused on marketing and Token Meter when you require tools for marketing.