Claude Code /usage MCP server credit: reading Sume spend
Claude Code 2.1.286 credits an MCP server for calls made while it was still connecting. Sume spend is a separate number: read it with usage_get.

The Claude Code 2.1.286 fix is about attribution: /usage now credits an MCP server for a tool call made while that server was still connecting, for example right after a restart. It does not change what Sume charges. To see Sume spend, call usage_get or balance_get on the Sume MCP server.
The changelog line is from the Claude Code changelog; the Sume tool names are from MCP tools and gates, both read 2026-10-01.
What changed in Claude Code /usage?
The 2.1.286 entry (September 30, 2026) says it fixed /usage not crediting an MCP server for a tool call made while that server was still connecting or had only just connected, such as right after a restart. The changelog says nothing more about the report, so treat it as a per-server tally of calls inside Claude Code.
Where does Sume spend show up?
Sume keeps its own account tools. The docs list balance_get and usage_get under Account and catalog, next to account_me and catalog_list. Both are read tools, so an OAuth session with only mcp:read can call them.
| Question | Where to look |
|---|---|
| Which MCP server did Claude Code credit for a call? | Claude Code /usage |
| How much balance is left on Sume? | balance_get |
| What did my Sume account use? | usage_get |
| What will this call cost before I run it? | dry_run on the paid tool |
How do I preflight a paid call?
The OAuth docs say paid and write submits need an idempotency_key, that an optional dry_run preflights cost, and that an optional max_spend_usd is enforced only when provided. Pair that with a read of balance_get before a long session. See also reading usage and balance in CI.
How do I connect Claude Code to Sume?
The quickstart command is claude mcp add --transport http sume https://mcp.sume.com/mcp, followed by claude mcp login sume. Then ask Claude to call a read-only tool such as usage_get to confirm the connection.
Sources
Related posts
More in Developers
- Claude Managed Agents auto permission and Sume paid MCP calls
The auto policy evaluates each MCP tool call server-side. Sume has no paid scope, so pair auto with dry_run, max_spend_usd and a scope-limited session.
- Claude Opus 5.5 tool_choice any 400: steer Sume tools instead
Opus 5.5 returns 400 for tool_choice any or tool. Use auto, then steer to generate_image with instructions and tools_schema, and keep dry_run before paid calls.
- Codex MCP input schema budget: how many Sume tools you load
Codex 0.158.0 makes MCP and Code Mode input schema budgets configurable. Sume keeps tool descriptions short and shows fewer tools to a read-only session.
- Apply a LUT to video by API: no .cube file, use lutrgb curves
Sume's video filter cannot load a .cube LUT because lut3d is not allowlisted. Per-channel curves with lutrgb or lutyuv are the supported way to grade.
Written by Sume