What is @vk0/agent Cost Mcp?
Local Cost Guard and runtime guardrails for AI agents in Claude Code. It reads your local JSONL session logs to show where spend is coming from, forecast where it is heading, attribute cost by provider/model/tool, roll up subagent trees, and let operators push signed monitor-webhook alerts—all without a hosted control plane, cloud, or API key.
How to use @vk0/agent Cost Mcp?
Install by adding an npx-based MCP server to your client configuration (Claude Desktop, Claude Code CLI, Cursor, or Cline). No global install required. Once configured, ask the agent “What tools does agent-cost expose?” to see the eleven available tools. Operates on existing session logs at ~/.claude/projects/.
Key features of @vk0/agent Cost Mcp
- Cost queries:
get_session_cost, get_tool_usage, get_cost_trend, get_subagent_tree
- Optimization analytics:
get_tool_roi, suggest_optimizations, detect_cost_anomalies
- Predictive tools:
get_cost_forecast, estimate_run_cost
- Configuration tools:
configure_budget, set_monitor_webhook
- Operates entirely locally on JSONL session logs from Claude Code
- Privacy-preserving with zero cloud dependencies
Use cases of @vk0/agent Cost Mcp
- Identify which tool, subagent, or branch burned the budget in a Claude Code session
- Catch retry loops and runaway patterns before costs compound silently
- Set budget thresholds and route monitor alerts for pre-spend guardrails
- Attribute cost across parent/subagent session trees with
get_subagent_tree
- Detect daily cost anomalies against a local baseline
コメント