Skip to main content

llmledger-mcp

Ask Claude (or Cursor, ChatGPT desktop, any app that speaks MCP) which AI model to use and what it costs, in the middle of your work. The answers come from llmledger: LiteLLM's public price catalogue, Arena's ratings by task, and every price change since 2023 with how likely a price is to change next. Rebuilt every day.

Install

Needs uv. Nothing to host and no keys: the plug-in runs on your computer and reads the day's data from the llmledger page, cached for a day, with a bundled copy for offline use.

Claude Code:

claude mcp add llmledger -- uvx llmledger-mcp

Claude Desktop (Settings, Developer, Edit config) or Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "llmledger": { "command": "uvx", "args": ["llmledger-mcp"] }
  }
}

A LiteLLM proxy can offer it to a whole team through its MCP gateway, as a stdio server with the same command.

What you can ask

Tool For example
suggest_for_project "Which model and effort for this project?" with the starting prompt; pay can be claude or chatgpt to compare within a plan
compare_models "Opus 5.5 or Fable 5.1 for coding, and when is Fable cheaper?"
estimate_cost "What do 2,000 calls a day of 10K tokens in and 1K out cost on these three?"
find_models "The best rated coding models under $10 per 1M answer tokens that read images"
price_history "Has Claude Opus 5.5's price changed, and how likely is it to change soon?"

Plus a resource, llmledger://snapshot (data dates and sources), and a prompt, pick_a_model.

Good to know

  • Costs and ratings are estimates. Arena ratings say which answers people preferred, not what will work best for you. Plan use (Claude, ChatGPT) assumes a plan runs down in step with API prices, because plans do not publish per-model limits. Not financial or procurement advice.
  • Effort levels come from LiteLLM; the suggested level is a rule of thumb. No open source measures tokens per task at each effort level yet.
  • Set LLMLEDGER_DATA to a local data.json or another address to use your own copy.

Data and licences

Prices: LiteLLM's model_prices_and_context_window.json (MIT). Ratings: the Arena leaderboard (CC BY 4.0). Price history and outlook: llmledger (MIT). Built with FastMCP (Apache-2.0). Independent; not affiliated with BerriAI, LiteLLM or Arena.

Metadata

Release files for llmledger-mcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for llmledger-mcp 0.1.1
File Size Uploaded
llmledger_mcp-0.1.1.tar.gz 318.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for llmledger-mcp 0.1.1
File Interpreter ABI Platform
llmledger_mcp-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 632.9 kB

Release files / llmledger_mcp-0.1.1.tar.gz

Download URL llmledger_mcp-0.1.1.tar.gz
Size 318.4 kB
Tags Source
SHA-256 checksum
How to use checksums
5b04ca584371aa811ee1e4fd4979d70f1c01ec6954e223463e270366f51aaee4
BLAKE2b-256 checksum
How to use checksums
9017f8b199b42e689508cc42ebe232020e070a878aabbb37cc9d5b3594fc4180
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Release files / llmledger_mcp-0.1.1-py3-none-any.whl

Download URL llmledger_mcp-0.1.1-py3-none-any.whl
Size 314.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
642c829833c91cb238455acdea73c836595095088ddd966cd425617e4d32ece6
BLAKE2b-256 checksum
How to use checksums
faf6c5eab7d7b878f9681d113adc6a3c58c34d2a216812e3cbec00d88d32dc6d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page