What is the key difference between MCPSpend and Sentry MCP?

MCPSpend belongs to the Monitoring category with local stdio execution, while Sentry MCP belongs to the Monitoring category with local stdio execution.

How do I install MCPSpend or Sentry MCP 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 MCPSpend and Sentry MCP free or paid?

MCPSpend operates under a Freemium model (API Key required). Sentry MCP operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

MCPSpend lists 6 tools with 3 views and 110 GitHub stars. Sentry MCP lists 6 tools with 3 views and 858 GitHub stars.

Can I use both MCPSpend and Sentry MCP 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

MCPSpend vs Sentry MCP

In-depth architectural comparison of the MCPSpend and Sentry MCP 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

MCPSpend

Monitoring · Local stdio

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

Sentry MCP

Monitoring · Local stdio

Quality: 49/100 (Fair) | Auth: API Key required

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

Which MCP Server Should You Choose?

Choose MCPSpend when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: Local stdio observability proxy, Per-tool and per-server usage attribution, MCP-based usage queries.

Explore MCPSpend Details

Choose Sentry MCP when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SENTRY_ACCESS_TOKEN, EMBEDDED_AGENT_PROVIDER, OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, OPENROUTER_MODEL, OPENROUTER_REASONING_EFFORT, SENTRY_HOST.
Primary tools included: .

Feature & Specification Comparison

Specification	MCPSpend andreisirbu91-lab Monitoring	Sentry MCP getsentry Monitoring
Summary	Real-time cost observability for MCP tool calls. Transparent proxy auto-detects every MCP client (Claude Desktop, Cursor, Windsurf, VS Code, Claude Code, Zed, Continue.dev, Cline, Goose) and attributes spend per tool, per project, per end-customer. npx @mcpspend/proxy add install. Free tier 25K calls/month, no card. MIT proxy on npm. EU-hosted, GDPR-ready.	Sentry.io integration for error tracking and performance monitoring
Category & Scope

Tools & Capabilities Breakdown

MCPSpend Tools (6)

Local stdio observability proxy

Per-tool and per-server usage attribution

MCP-based usage queries

Dashboard with sessions and CSV export

Metadata-only telemetry for tool calls

HTTP and stdio MCP access

Sentry MCP Tools (6)

Remote MCP access through mcp.sentry.dev

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).

MCPSpend Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "andreisirbu91-lab-mcpspend": {
      "command": "npx",
      "args": [
        "-y",
        "@mcpspend/proxy"
      ]
    }
  }
}

Sentry MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "getsentry-sentry-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server@latest"
      ],
      "env": {
        "SENTRY_ACCESS_TOKEN": "YOUR_SENTRY_ACCESS_TOKEN_HERE",
        "EMBEDDED_AGENT_PROVIDER": "YOUR_EMBEDDED_AGENT_PROVIDER_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
        "OPENROUTER_MODEL": "YOUR_OPENROUTER_MODEL_HERE",
        "OPENROUTER_REASONING_EFFORT": "YOUR_OPENROUTER_REASONING_EFFORT_HERE",
        "SENTRY_HOST": "YOUR_SENTRY_HOST_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCPSpend is categorized under Monitoring and uses a local stdio subprocess. In contrast, Sentry MCP belongs to Monitoring using local stdio subprocess. Select MCPSpend when you need capabilities focused on monitoring and Sentry MCP when you require tools for monitoring.

More alternatives to MCPSpend More alternatives to Sentry MCP Monitoring category hub