
Agent Costcenter MCP
- Updated April 24, 2026
- mdfifty50-boop/agent-costcenter-mcp
io.github.mdfifty50-boop/agent-costcenter is an MCP server that tracks multi-agent billing and cost allocation through MCP.
About
io.github.mdfifty50-boop/agent-costcenter is a Model Context Protocol server focused on multi-agent billing and cost allocation tracking. Developers who run several agents—research, codegen, review, support—often discover API invoices that are impossible to attribute to a single workflow. This MCP server exposes cost-center concepts through stdio so your coding agent can record, query, or reason about spend by agent or workload during iteration and analytics reviews. Install the npm package agent-costcenter-mcp locally alongside Claude Code or Cursor, wire it as a stdio MCP entry, and use it when you are optimizing token burn rather than shipping net-new UI. It pairs naturally with multi-agent bridges and orchestration experiments but does not process payments or replace cloud billing consoles. Intermediate complexity reflects the need to define allocation rules and keep local data consistent. Use it when agent economics become a shipping constraint, not on day one of idea validation.
- Multi-agent billing and cost allocation tracking via MCP tools
- npm package agent-costcenter-mcp v0.1.3 with stdio local transport
- Designed for fleets of agents where per-agent attribution replaces one blended API bill
- Fits operate-phase iteration when you throttle or refactor expensive agent paths
- Source on GitHub at mdfifty50-boop/agent-costcenter-mcp for customization
Agent Costcenter MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add agent-costcenter-mcp -- npx -y agent-costcenter-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | agent-costcenter-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | April 24, 2026 |
| Repository | mdfifty50-boop/agent-costcenter-mcp ↗ |
What it does
Track and allocate LLM or agent spend across multiple agents so developers see who burned budget and why.
Who is it for?
Best when you're running multiple MCP agents and need attribution before scaling usage or adding paid features.
Skip if: Skip if you only run a single cheap agent or already use enterprise FinOps dashboards with full cloud integration.
What you get
Cost allocation data is available via MCP so you can iterate agent designs with per-agent billing visibility instead of guessing from aggregate invoices.
- MCP-accessible cost and allocation records per agent context
- Clearer decisions when trimming or merging agent roles
- Local cost-center integration without a separate FinOps SaaS
By the numbers
- Version 0.1.3 in server manifest
- npm identifier agent-costcenter-mcp with stdio transport
- Repository https://github.com/mdfifty50-boop/agent-costcenter-mcp
README.md
agent-costcenter-mcp
MCP server for per-agent cost attribution and budget management. Answer "which agent costs the most?" across your entire AI agent fleet.
Features
- Per-agent cost tracking — register agents, log LLM and tool calls, get per-agent spend
- Built-in pricing table — 11 models (Claude, GPT, Gemini, DeepSeek) with fuzzy name matching
- Budget management — set caps and alerts, check remaining budget, warn or block on overspend
- Cost reports — breakdown by agent, team, project, or all; includes model-level detail and percentages
- Anomaly detection — automatically flag agents with 2x+ spending spikes
- Model comparison — compare cost-per-1K-tokens across all models used
Quick Start
npx agent-costcenter-mcp
Claude Desktop
{
"mcpServers": {
"agent-costcenter": {
"command": "npx",
"args": ["agent-costcenter-mcp"]
}
}
}
Tools
| Tool | Description |
|---|---|
register_agent |
Register agent with team, project, model, and budget cap |
log_llm_call |
Log an LLM call — auto-calculates cost from pricing table |
log_tool_call |
Log a tool/API call cost |
get_cost_report |
Cost breakdown by agent, team, project, or all |
set_budget_alert |
Set spending threshold (warn or block) |
check_budget |
Check if agent is within budget |
get_cost_anomalies |
Find agents with unusual spending spikes |
compare_models |
Compare cost efficiency across models |
Resources
| URI | Description |
|---|---|
costcenter://summary |
Current total spend across all agents |
costcenter://pricing |
Built-in model pricing table |
Built-in Pricing (per 1M tokens)
| Model | Input | Output |
|---|---|---|
| claude-opus-4 | $15.00 | $75.00 |
| claude-sonnet-4 | $3.00 | $15.00 |
| claude-haiku-4 | $0.80 | $4.00 |
| gpt-4o | $2.50 | $10.00 |
| gpt-4o-mini | $0.15 | $0.60 |
| gpt-4.1 | $2.00 | $8.00 |
| gpt-4.1-mini | $0.40 | $1.60 |
| gemini-2.5-pro | $1.25 | $10.00 |
| gemini-2.5-flash | $0.15 | $0.60 |
| deepseek-v3 | $0.27 | $1.10 |
| deepseek-r1 | $0.55 | $2.19 |
Model names are fuzzy-matched (case-insensitive, strips version suffixes).
Example Workflow
1. register_agent(agent_id="researcher", team="discovery", model="claude-sonnet-4", budget_cap_usd=10)
2. log_llm_call(agent_id="researcher", model="claude-sonnet-4", input_tokens=5000, output_tokens=2000)
3. log_tool_call(agent_id="researcher", tool_name="web_search", duration_ms=1200, cost_usd=0.01)
4. check_budget(agent_id="researcher")
5. get_cost_report(scope="all")
6. get_cost_anomalies()
7. compare_models()
Development
npm install
npm test
npm run dev # watch mode
License
MIT
Recommended MCP Servers
How it compares
MCP cost-allocation tooling for agent fleets, not payment processing or generic cloud cost MCPs alone.
FAQ
Who is io.github.mdfifty50-boop/agent-costcenter for?
Developers operating multiple AI agents who need billing and allocation tracking exposed to their MCP-enabled coding assistant.
When should I use io.github.mdfifty50-boop/agent-costcenter?
Use it during operate and grow reviews when token costs climb and you must allocate spend per agent before changing prompts or architecture.
How do I add io.github.mdfifty50-boop/agent-costcenter to my agent?
Install agent-costcenter-mcp from npm, configure it as a stdio MCP server in your client, and enable the cost tracking tools after restart.