teamspend
Related Servers
Alternatives to teamspend
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA local-first, multi-provider cost meter for LLM usage, exposed as MCP tools. Captures every call into a local SQLite ledger and lets any coding agent query spend, compare providers, and get recommendations — no cloud, no account. First-class support for Chinese providers (Qwen, DeepSeek) alongside Anthropic and OpenAI.723 PyPI4MIT
- AlicenseBqualityCmaintenanceAn MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.10MIT
- AlicenseAqualityAmaintenanceLocal-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs579 npm1MIT
- AlicenseBqualityFmaintenanceTrack LLM token costs across Claude, GPT and Gemini. MCP server + CLI with optimization hints and $ savings estimates.83 npm1MIT
- AlicenseAqualityAmaintenancePrices your Claude Code and Codex sessions from the transcripts on disk, shows what each agent cost over any period, and tells you in plain English what would have been cheaper. CLI, Browser UI and MCP server.85MIT
- AlicenseAqualityDmaintenanceMCP server for querying OpenAI usage and cost data, including spend summaries, daily breakdowns, month-over-month comparisons, and token usage by model.3MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another. The tool's description clearly limits its purpose to a specific before/after cost comparison, so an agent cannot misselect it for anything else.
There is only one tool named 'run', so there is no inconsistency in naming conventions. However, the name is very generic and does not convey the tool's specific function, which is a minor weakness since a descriptive name would be more helpful.
The server exposes only one tool, which is below the typical 3-15 range. While the tool is substantial and covers a focused use case, the single-tool surface feels thin for a server, though it is not an extreme mismatch because the tool is not trivial.
Within its declared scope of comparing AI-coding-tool spend between two windows, the tool provides a complete workflow including error handling for missing credentials and a report file. Minor gaps like lacking multi-tool comparison or raw spend analytics don't affect its stated purpose.