Cursor Usage vs Claude MCP Bridge
A side-by-side look at the Cursor Usage and Claude MCP Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cursor Usage for coding agents work as a local process; choose Claude MCP Bridge for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cursor Usage when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CURSOR_API_KEY. - You want tools like
get_team_members, get_spending, get_daily_usage.
Choose Claude MCP Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
query, structured, search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 59/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | CURSOR_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 7 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 17 | 5 |
| Full listing | View Cursor Usage | View Claude MCP Bridge |
Tools & capabilities
Cursor Usage tools 17
get_team_membersList all team members with their roles and status. Returns name, email, role, and whether they've been removed.get_spendingGet current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits.get_daily_usageGet daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions.get_billing_groupsGet billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates.get_usage_eventsGet granular per-request usage events with model, token counts, costs, and whether the request was chargeable. Supports filtering by user email and date range.set_spend_limitSet a hard spending limit (in dollars) for a specific team member. Use with caution — this will block the user from making requests once the limit is reached.get_dauGet daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage.get_model_usageGet model usage breakdown per day: which models are being used, how many messages, and by how many users. Essential for understanding model adoption and cost drivers.get_agent_editsGet agent edit metrics: suggested vs accepted vs rejected diffs and lines. Shows how effectively the team is using AI-generated code.get_tabsGet tab autocomplete usage: suggestions shown vs accepted vs rejected, with line-level detail.get_mcp_usageGet MCP (Model Context Protocol) tool usage: which MCP servers and tools are being used, and how often.get_file_extensionsGet top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects.- +5 more on the listing page
Claude MCP Bridge tools 5
queryExecute a prompt via Claude Code CLI with optional file context and session resume. Claude is an AI coding agent that can generate, analyze, refactor, and explain code. Capabilities: code generation and refactoring, code analysis and explanation, file understanding (text and images), multi-turn conversations via sessionId. Cost: Default model is Sonnet (~$0.01-0.10/call). Use effort="low" for simple tasks, effort="high" + model="opus" for complex analysis. Set maxBudgetUsd to cap per-call cost (recommended for effort="max" or model="opus"). Tips: - Set workingDirectory to the target repo for project-aware responses. - Break complex tasks into focused prompts rather than one large request. - Resume multi-turn conversations with sessionId from a previous response's metadata. - Include relevant files via the files parameter for targeted context (text files inlined in prompt, images trigger allowed-tools mode). - Use noSessionPersistence=true for stateless one-shot calls.structuredGenerate JSON conforming to a provided JSON Schema. Uses Claude CLI's native --json-schema flag for validated output (not client-side validation). Use for: data extraction from text/files, classification, entity parsing, or any task needing machine-parseable output. Cost: Similar to query (~$0.01-0.10/call). Schema complexity doesn't significantly affect cost. Tips: - Pass the JSON Schema as a JSON string in the schema parameter. - Schema max size: 20KB. Keep schemas focused for reliable output. - For extraction tasks, include source text via the files parameter or inline in the prompt.searchWeb search via Claude Code CLI using WebSearch and WebFetch tools. Searches the web and synthesizes a comprehensive answer with source URLs. Use for: current information, documentation lookups, API references, comparing libraries, and research questions. Cost: Typically ~$0.02-0.05/search with Sonnet. Tips: - Ask specific, focused questions for best results. - Results include source URLs for verification. - Use maxResponseLength to control response verbosity. - Increase timeout for complex research queries that may require multiple web fetches.listSessionsList active Claude CLI sessions tracked by this server. Returns session metadata (IDs, models, timing, turn counts, cumulative cost) for orchestration. Use to check available sessions before resuming with sessionId. No cost (local lookup only).pingHealth check: verifies Claude CLI is installed and authenticated, reports versions, capabilities, and configuration. No cost (local check only).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cursor Usage
{
"mcpServers": {
"ofershap-cursor-usage": {
"command": "npx",
"args": [
"-y",
"cursor-usage-mcp"
],
"env": {
"CURSOR_API_KEY": "YOUR_CURSOR_API_KEY_HERE"
}
}
}
}
Claude MCP Bridge
{
"mcpServers": {
"hampsterx-claude-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"claude-mcp-bridge"
]
}
}
}
Frequently asked questions
Cursor Usage is categorized under Coding Agents and uses a local stdio subprocess. Claude MCP Bridge belongs to Coding Agents and uses a local stdio subprocess. Pick Cursor Usage for coding agents work and Claude MCP Bridge for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cursor Usage is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Claude MCP Bridge is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ofershap-cursor-usage and hampsterx-claude-mcp-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cursor Usage has a quality signal of 59/100 (Good) with 1 views, 0 installs and 8 GitHub stars. Claude MCP Bridge has 64/100 (Good) with 6 views, 0 installs and 7 GitHub stars.