What is the key difference between Cursor Usage and Llm Router?

Cursor Usage belongs to the Developer Tools category with local stdio execution, while Llm Router belongs to the Developer Tools category with local stdio execution.

How do I install Cursor Usage or Llm Router 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 Cursor Usage and Llm Router free or paid?

Cursor Usage operates under a BYOK (Pay Provider Direct) model (API Key required). Llm Router operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Cursor Usage lists 17 tools with 1 views and 8 GitHub stars. Llm Router lists 6 tools with 3 views and 79 GitHub stars.

Can I use both Cursor Usage and Llm Router 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

Cursor Usage vs Llm Router

In-depth architectural comparison of the Cursor Usage and Llm Router 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

Cursor Usage

Developer Tools · Local stdio

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

Llm Router

Developer Tools · Local stdio

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

Verdict Summary: Choose Cursor Usage if you need specialized Developer Tools tools running via a local process. Choose Llm Router if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Cursor Usage when:

You need dedicated capabilities in the Developer Tools 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: CURSOR_API_KEY.
Primary tools included: get_team_members, get_spending, get_daily_usage.

Explore Cursor Usage Details

Choose Llm Router when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OPENAI_API_KEY, GEMINI_API_KEY, OLLAMA_BASE_URL, OPENROUTER_API_KEY.
Primary tools included: Complexity- and cost-aware model routing, Claude subscription quota protection, Support for 20+ model providers.

Feature & Specification Comparison

Specification	Cursor Usage ofershap Developer Tools	Llm Router ypollak2 Developer Tools
Summary	Enterprise AI coding usage analytics — track spend, model usage, and costs across Cursor/Claude Code sessions via MCP server	Subscription-aware LLM router for Claude Code. Routes tasks to 20+ providers (OpenAI, Gemini, Groq, Ollama, Codex) based on complexity classification, Claude subscription pressure, and cost. Free tasks stay on Claude subscription; expensive tasks fall back to the cheapest capable model. Includes 30 MCP tools, 6 auto-routing hooks, semantic dedup cache, prompt caching, daily spend cap, and a live web dashboard.
Category & Scope

Tools & Capabilities Breakdown

Cursor Usage Tools (17)

get_team_members

List all team members with roles and status

get_spending

Current billing cycle spend per member

get_daily_usage

Daily usage data: lines, requests, models, modes

get_billing_groups

Billing groups with member lists and spend

get_usage_events

Per-request events with model, tokens, and costs

set_spend_limit

Set a hard spending limit for a user

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

Cursor Usage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ofershap-cursor-usage": {
      "command": "npx",
      "args": [
        "-y",
        "cursor-usage-mcp"
      ],
      "env": {
        "CURSOR_API_KEY": "YOUR_CURSOR_API_KEY_HERE"
      }
    }
  }
}

Llm Router Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ypollak2-llm-router": {
      "command": "uvx",
      "args": [
        "llm-routing"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
        "OLLAMA_BASE_URL": "YOUR_OLLAMA_BASE_URL_HERE",
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Cursor Usage is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Llm Router belongs to Developer Tools using local stdio subprocess. Select Cursor Usage when you need capabilities focused on developer tools and Llm Router when you require tools for developer tools.

More alternatives to Cursor Usage More alternatives to Llm Router Developer Tools category hub