llmkit-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMKIT_API_KEY | No | LLMKit API key from the dashboard. Optional for local tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| llmkit_usage_statsC | Get usage statistics (spend, requests, top models) for a time period |
| llmkit_cost_queryB | Query cost breakdown grouped by provider, model, session, or day |
| llmkit_list_keysA | List all API keys with status and creation date |
| llmkit_budget_statusA | Check budget limits and remaining balance |
| llmkit_healthA | Check proxy health and response time |
| llmkit_session_summaryA | Get recent proxy sessions with cost, duration, and models used |
| llmkit_local_sessionA | Current session cost across all detected AI coding tools (Claude Code, Cline). No API key needed. |
| llmkit_local_projectsA | Cumulative cost across all projects and sessions from all detected AI coding tools, ranked by spend. |
| llmkit_local_cacheA | Cache savings analysis across all detected AI coding tools. Shows how much prompt caching saved. |
| llmkit_local_forecastA | Monthly cost projection based on local AI tool usage. Compares to Max subscription. |
| llmkit_local_agentsA | Subagent cost attribution for the current Claude Code session. Shows which agents cost the most. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cost-report | Generate a cost report for a time period |
| budget-check | Check all budgets and warn about any approaching limits |
| session-summary | Summarize costs and usage for the current coding session |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Session Cost Dashboard |
TDQS
Scored across 11 tools
Tools are mostly distinct, targeting different aspects like budget, cost breakdown, health, keys, local session, etc. However, llmkit_cost_query, llmkit_usage_stats, and llmkit_session_summary have overlapping purposes (cost/spend/usage data) which could cause some confusion.
All tools follow a consistent pattern with the 'llmkit_' prefix and descriptive noun phrases separated by underscores, e.g., llmkit_budget_status, llmkit_cost_query. No mixing of conventions.
With 11 tools, the count is well within the recommended 3-15 range. Each tool covers a distinct aspect of proxy cost monitoring and management, justifying its inclusion.
The tool surface covers major monitoring needs: health, budget, cost, keys, sessions, and local attribution. However, it lacks management capabilities (e.g., create/update keys or budgets) and could include actions like setting usage limits, which are minor gaps for a read-only analytics server.