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_DATAto 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.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llmledger_mcp-0.1.0.tar.gz | 318.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llmledger_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 632.6 kB
Release files / llmledger_mcp-0.1.0.tar.gz
| Download URL | llmledger_mcp-0.1.0.tar.gz |
|---|---|
| Size | 318.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ccdb19add24c10c84fe7c5a9180a9de8cb18d5bff62c99a527f6ff159abbdc1
|
|
BLAKE2b-256 checksum How to use checksums |
bdf9a27f91f312a0db30cd76ac0d82dc1ccc365a3ea9a595225ef1beb5604fa2
|
| 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 logRelease files / llmledger_mcp-0.1.0-py3-none-any.whl
| Download URL | llmledger_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 314.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93c85716cc4de8040858d92df8b3a91eb9d5a84dbb4df20cc6321e3f691887b8
|
|
BLAKE2b-256 checksum How to use checksums |
ee4e5fb85957a762a08df4db50c163f8f7c43bf906e1a2670f40e7a9cd4d9e59
|
| 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