Tokenscope MCP Server

MCP server for tokenscope — let AI agents analyze Claude Code session cost & context attribution (reuses tokenscope's engine; local, read-only). Exposed over MCP by the tokenscope mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

tokenscope ⏣ latest session ────────────────────────────────────────────────────── Total cost $868.84 over 967 model turns

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• repo — https://github.com/wartzar-bee/tokenscope
• v0.1 — Claude Code session cost + context attribution + insights. 20/20 unit tests on the cost math (npm test)

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tokenscope mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tokenscope's toolset — repo, v0.1 — is a fair guide to whether it matches your workflow. It is maintained by wartzar-bee; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.