Llmkit

What smigolsmigol/llmkit does

The smigolsmigol/llmkit MCP server brings LLMKit cost and session data into an MCP client. It is intended for the 💻 Developer Tools category and exposes two groups of capabilities:

• Five local tools inspect supported Claude Code sessions and Cline task data without requiring an LLMKit account or API key.
• Six gateway tools query spend, budgets, keys, sessions, and service health when an existing key is available.

Together, the MCP package exposes 11 tools. The local surface is useful for reviewing coding activity on the machine where the client runs. The gateway surface is for account-level or service-level information, including spend analytics and budget status.

The broader LLMKit project also provides local Python tracking, a command-line wrapper, TypeScript and AI SDK packages, and an HTTP gateway. Those surfaces are separate from the MCP server, but they provide context for how cost data can be produced and managed.

How it works

The smigolsmigol/llmkit MCP server is launched as an npm package through an MCP client's stdio transport. Local tools read supported Claude Code session and Cline task data directly, so they do not need an LLMKit account or proxy.

Gateway tools communicate with the LLMKit service and are enabled when LLMKIT_API_KEY contains an existing key. The gateway's request path estimates spend before provider dispatch, rejects requests that do not fit the active budget, and settles admitted reservations against actual usage after completion. The MCP tools query the resulting spend, budget, session, key, and health information; they are not described as a replacement for the gateway or provider SDKs.

LLMKit's pricing catalog is a bundled reference snapshot rather than a live provider quote. Estimates can differ from provider invoices because billing rules, model modality, and catalog freshness remain relevant.

Setup and configuration

Add the package to an MCP client using a stdio entry such as:

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

For local session and task inspection, this configuration does not require an LLMKit key. Gateway functionality requires an existing LLMKIT_API_KEY. The repository states that account creation and key management are temporarily unavailable while the authenticated service is being restored, so a new user without an existing key should use the local tracking paths instead.

Tools and capabilities

The smigolsmigol/llmkit MCP server supports these documented capability areas:

• Inspect supported Claude Code sessions.
• Inspect Cline task data.
• Query spend and cost analytics.
• Monitor budgets.
• Query session information.
• Manage or query API keys through gateway tools.
• Check service health.

Gateway access depends on the authenticated LLMKit service, while local inspection is designed to work without an account.

Limitations and notes

The MCP package does not make the pricing catalog a live quote or guarantee invoice-level accuracy. The public comparison endpoint prices only the exact model keys supplied to it and does not select or recommend the cheapest model.

Gateway examples require a pre-existing key. Local tools have a narrower scope: they inspect supported Claude Code and Cline records rather than providing unrestricted access to all coding-session formats.

Choose smigolsmigol/llmkit when the MCP client needs documented LLMKit spend, budget, session, key, or health data. Choose the project's Python transport or CLI when the primary requirement is local request tracking around existing provider clients.