MCP / local evidence

Ask your coding agent what the session cost.

Eleven cost tools in one MCP server. Five inspect supported local Claude Code and Cline data without an account, a proxy, or an API key.

local tools

proxy tools

install

$ npx @f3d1/llmkit-mcp-server

Add to your MCP client config

.mcp.json (Claude Code) or .cursor/mcp.json (Cursor)

{
  "mcpServers": {
    "llmkit": {
      "command": "npx",
      "args": ["-y", "@f3d1/llmkit-mcp-server"]
    }
  }
}

No API key is needed for local tools. Proxy tools require an existing key in LLMKIT_API_KEY while new account creation is closed.

Local tools no account needed

Reads supported Claude Code sessions and Cline task data from detected editor storage.

llmkit_local_session

Current Claude Code session and latest detected Cline task cost

llmkit_local_projects

Cumulative cost per project, ranked by spend

llmkit_local_cache

Cache savings analysis: how much prompt caching saved

llmkit_local_forecast

30-day API-rate projection from the detected local history

llmkit_local_agents

Claude Code subagent attribution for the current session

Queries your LLMKit proxy for spend, budgets, and sessions.

llmkit_usage_stats

Spend, requests, top models for a time period

llmkit_cost_query

Cost breakdown by provider, model, session, or day

llmkit_budget_status

Budget limits and remaining balance

llmkit_session_summary

Recent sessions with cost, duration, models

llmkit_list_keys

Configured gateway key metadata and status

llmkit_health

Proxy health and response time

Claude Code

Reads local JSONL sessions with token and cache-usage fields

Cline on VS Code

Reads Cline task data from extension global storage

Cline on Cursor / Windsurf

Detects the same Cline extension storage in supported editor variants

Remote editor installs

Checks supported VS Code, Cursor, and Windsurf server directories

WSL from Windows

Checks reachable WSL home directories for supported remote editor storage