skillfm-claude-code-token-usage-mcp
by ericm1018
README.md
# SkillFM Claude Code Token Usage MCP
**Claude Code token usage and cost visibility for MCP-capable agents.**
This repository is a transparent SkillFM gateway package. It exists to match a specific marketplace/search intent, then delegates execution to the canonical [SkillFM Beacon MCP](https://www.npmjs.com/package/@skillfm/mcp) and local runtime.
Powered by SkillFM Beacon.
## Quick Start
Use this gateway as an MCP stdio server:
```bash
npx -y @skillfm/claude-code-token-usage-mcp@latest
```
Equivalent explicit SkillFM entrypoint:
```bash
npx -y @skillfm/mcp@latest
```
For MCP clients that accept JSON config:
```json
{
"mcpServers": {
"claude-code-token-usage": {
"command": "npx",
"args": ["-y", "@skillfm/claude-code-token-usage-mcp@latest"]
}
}
}
```
## What This Gateway Helps With
- Inspect Claude Code token usage and estimated cost signals.
- Connect usage visibility to SkillFM Beacon AI health checks.
- Find repeated context, stale sessions, and cost-saving opportunities.
- Route users toward local-first SkillFM activation without asking for provider keys first.
This gateway is for users who ask:
- "How many Claude Code tokens did I use today?"
- "Why did my Claude Code usage spike?"
- "Which sessions or projects are wasting context?"
- "Can my agent show me token usage before I connect provider keys?"
## How It Works
The public package is intentionally thin. It sets `SKILLFM_GATEWAY_SOURCE=claude-code-token-usage` and forwards execution to `@skillfm/mcp@latest`, which then delegates to the canonical `@skillfm/local` runtime.
No private SkillFM platform logic, customer data, provider credentials, or backend modules live in this repository.
## Activation Path
Start the local sidecar when the user wants to connect SkillFM:
```bash
npx -y @skillfm/claude-code-token-usage-mcp@latest start
```
Agent-driven activation flow:
1. Read the sidecar URL from stdout or `~/.skillfm/local.json`.
2. Call `POST <sidecar_url>/activate/start`.
3. Show the returned verification URL and real device code to the user.
4. Poll `POST <sidecar_url>/activate/poll` until it returns `activated: true`.
5. Use SkillFM Beacon MCP tools for checkups, usage visibility, BYOK guidance, and cleanup audits.
Do not fabricate a placeholder code. The device code must come from `POST /activate/start`.
## Security Model
- **Transparent gateway**: This package is a public search/distribution gateway, not a separate hidden product.
- **Local-first runtime**: Runtime execution goes through SkillFM's local package.
- **BYOK boundary**: Provider keys are introduced only after user value is established, and key values are not read back by agents.
- **No private core**: This repository contains distribution metadata, docs, and a thin launcher only.
- **Read-only first**: Cleanup and usage inspection begin with read-only audits.
See [PRIVACY.md](./PRIVACY.md) and [SECURITY.md](./SECURITY.md).
## Marketplace Keywords
Claude Code token usage, Claude usage, token cost, LLM cost, AI health checkup, agent monitoring, context cleanup, SkillFM Beacon, MCP server.
Expected Official MCP Registry single-token hits:
- `claude-code`
- `token`
- `usage`
- `cost`
- `skillfm`
## License
MIT
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues