Skip to main content
Glama
TokenLens MCP Server

TokenLens MCP Server

by flikQ

TokenLens MCP Server

MCP server that exposes TokenLens pricing data as tools for AI agents (Claude Code, Cursor, Windsurf, Claude Desktop, etc.).

Tools

Tool

Description

compare_plans

Rank all plans by effective cost/1M tokens for a given model

run_scenario

Calculate API vs subscription cost for a usage pattern

break_even

Find the daily hours where API cost equals a subscription price

recommend_plan

Single best-value plan for your usage profile

Related MCP server: ohmytoken

Setup

1. Install

git clone https://github.com/flikQ/tokenlens-mcp.git
cd tokenlens-mcp
npm install   # or: bun install
npm run build # or: bun run build

2. Connect to your editor

Claude Code (one command):

claude mcp add tokenlens -- node /path/to/tokenlens-mcp/dist/index.js

To always use live pricing data from tokenlens.flikq.dev:

claude mcp add tokenlens -- env TOKENLENS_DATA_URL=https://tokenlens.flikq.dev/api/data node /path/to/tokenlens-mcp/dist/index.js

Cursor · Windsurf · Claude Desktop — add to config JSON:

  • Cursor: ~/.cursor/mcp.json

  • Windsurf: ~/.codeium/windsurf/mcp_config.json

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tokenlens": {
      "command": "node",
      "args": ["/path/to/tokenlens-mcp/dist/index.js"],
      "env": {
        "TOKENLENS_DATA_URL": "https://tokenlens.flikq.dev/api/data"
      }
    }
  }
}

3. Verify

Restart your editor, then ask your agent:

Use the tokenlens recommend_plan tool. I code 3h/day on claude-sonnet.

Data source

By default the server reads bundled data/*.json files from the repo. To always use the latest live pricing data, set:

TOKENLENS_DATA_URL=https://tokenlens.flikq.dev/api/data

The server fetches all data at startup and caches it in memory. If the URL is unreachable it automatically falls back to the bundled local files.

You can also point at a custom data directory:

TOKENLENS_DATA_DIR=/path/to/custom/data

License

MIT

Available Tools

4 tools
break_evenA

Find the daily usage hours at which API cost equals a subscription price. Below this threshold, the API is cheaper; above it, the subscription wins.

Inputs: plan_id (required), model_id, output_ratio, days_per_month, +1 more.

compare_plansA

Rank all TokenLens plans by effective cost per 1M tokens. Useful when choosing between subscriptions and API access for a given model.

Inputs: model_id, output_ratio.

recommend_planA

Get a single best-value plan recommendation for your usage profile. Considers whether a subscription or API access is cheaper, and whether token caps are sufficient.

Inputs: hours_per_day (required), model_id, output_ratio, days_per_month, +2 more.

run_scenarioA

Calculate total monthly token usage and cost (API vs subscription) for a given usage pattern. Returns costs for all matching plans side-by-side.

Inputs: hours_per_day (required), model_id, output_ratio, days_per_month, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: comparing plan costs, simulating usage scenarios, computing break-even thresholds, and generating personalized recommendations. Their descriptions make the boundary between them obvious.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: compare_plans, run_scenario, break_even, recommend_plan. No mixed styles or vague verbs.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of analyzing TokenLens plans. Each tool contributes a distinct analysis capability without redundancy.

    Completeness5/5

    The tool set covers all key aspects of plan selection: cost comparison, usage simulation, break-even analysis, and final recommendation. There are no obvious missing operations for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time AI model pricing, cost estimation, and budget management tools to help agents understand and optimize their spending. It enables agents to compare costs across multiple providers and select the most cost-effective models for specific tasks.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to fetch live, dated prices for LLM models and cloud compute instances across providers, compare and recommend models, and estimate monthly costs based on workload-specific token shapes and constraints.
      MIT