Skip to main content
Glama
pihme

claude-budget-mcp

by pihme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLAUDE_CONFIG_DIRNoDirectory containing .credentials.json. If set, reads $CLAUDE_CONFIG_DIR/.credentials.json; otherwise defaults to ~/.claude/.credentials.json.
CLAUDE_BUDGET_MCP_BASE_URLNoOverride the base URL of the usage endpoint (for tests or a proxy).

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_budgetA

Return the Claude subscription's usage limits (same figures as /usage): the 5-hour session window (session_*) and the weekly window across all models (weekly_*), each with used and remaining percent and reset time. windows lists every window found, including per-model weekly limits, so you can pick the relevant one. Data comes from an UNOFFICIAL, undocumented endpoint; null fields plus warning mean partial data. Call it once before expensive work; do not poll in a loop.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or misselection. The single tool's purpose is clear and distinct.

Naming Consistency5/5

The tool name 'get_budget' follows a clear verb_noun snake_case convention. With only one tool, consistency is trivially maintained.

Tool Count4/5

One tool is slightly under the typical 3-15 range, but it perfectly matches the narrow read-only scope of fetching a single usage endpoint. No additional tools are needed for the stated purpose.

Completeness4/5

The tool covers the core read operation for subscription usage limits, including session and weekly windows with detailed fields. However, it lacks any write or management operations for budgets or alerts, which the server name might imply.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources