What does it do vs a router?
It is a cost meter, not a router. It tells you what you spent and which provider fits a workload, but never changes your calls. It pairs happily alongside a router or a model-leaderboard tool.

@zhaoyue722
Basic information
A local-first, multi-provider cost meter for LLM usage, exposed as MCP tools. Captures every call into a local SQLite ledger and lets any coding agent query spend, compare providers, and get recommendations — no cloud, no account. First-class support for Chinese providers (Qwen,
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"llm-usage": {
"command": "uvx",
"args": [
"llm-usage-mcp"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Llm Usage & Cost Tracker is a local-first MCP server and CLI that captures LLM API calls across multiple providers (Anthropic, OpenAI, DeepSeek, Qwen), calculates costs, and answers spend queries through an agent or terminal. It is a cost meter, not a router.
Install via uv tool install llm-usage-mcp (or clone from source). Set at least one provider API key as an environment variable. Run the capture proxy (llm-usage-proxy), which listens on 127.0.0.1:5525. Point your LLM client’s base URL to the proxy. Use the MCP server (e.g., claude mcp add llm-usage -- uv run llm-usage-mcp) to ask agent questions, or run CLI commands like llm-usage spend, llm-usage compare, and llm-usage recommend.
It is a cost meter, not a router. It tells you what you spent and which provider fits a workload, but never changes your calls. It pairs happily alongside a router or a model-leaderboard tool.
Python 3.13+, uv or pipx for installation. SQLite is built into Python, no extra database setup.
All data is stored locally in a SQLite file at `~/.llm-usage/usage.db`.
Anthropic, OpenAI, DeepSeek, and Qwen are supported for both streaming and non-streaming. More providers (Gemini, Bedrock, Moonshot) are planned.
API keys are set as environment variables (e.g., `ANTHROPIC_API_KEY`). The proxy holds keys server-side; clients point their base URL at `http://127.0.0.1:5525` and never need keys directly.
Read public Instagram profiles and post feeds by handle in Claude, Cursor, and other MCP clients. Get follower counts, captions, hashtags, mentions, and engagement counts as structured JSON.
NetFoundry LLM Gateway is an OpenAI-compatible API proxy that routes requests across multiple LLM providers using zero-trust networking. Zero trust LLM gateway. OpenAI-compatible proxy with semantic routing and load bala

MCP server for managing Gologin browser profiles, proxies, fingerprints and cloud browser sessions through AI conversations
The video infra for AI agents: compose motion-graphics video from one JSON document (open Clipkit Protocol), validate before it costs anything, preview stills in-chat, and render deterministic MP4s on a GPU runtime.
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.
Comments