Teamspend MCP server
Compares AI coding tool spend before and after a migration via MCP tools.
0 stars
Reviews
Write oneNobody has reviewed Teamspend yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Teamspend tools (1, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
runwrite actionRun the teamspend CLI with `args` (e.g. ["--tools", "claude-code-personal,opencode", "--before", "2020-01-01:2020-01-31", "--after", "2020-02-01:2020-02-28"]) and return its parsed `--json` output. `--json` is appended automatically, callers should not pass it themselves.
Public scan report
scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 11 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the Teamspend repository's README, as published. We do not edit it. Read it on GitHub
teamspend
<!-- mcp-name: io.github.RudrenduPaul/teamspend --> <!-- Ownership-proof string for registry.modelcontextprotocol.io publishing. Do not remove. -->
Install • Usage • Features • Compare • FAQ • Contributing
Your AI coding tools will never tell you if switching between them actually saved money. teamspend does, in one command.
The recording above uses claude-code-personal (credential-free, reads local session logs) so the install-to-first-run flow plays end to end with no admin API keys required; the live output shape is identical whichever adapter you point it at.
npx teamspend-cli --tools cursor,claude-code --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30Six tools now, not two: Cursor, Claude Code, GitHub Copilot, OpenCode, and Codex CLI, plus a credential-free personal mode for anyone without admin access. More teams are running more than one AI coding tool at once, or moving between them, than ever before. Every one of those tools has a dashboard that's perfectly accurate about itself and structurally incapable of showing you anything else. teamspend is the missing piece: one real number, pulled straight from both tools' own APIs, showing exactly what changed.
Table of contents
- See it in action
- What it actually does
- Get started in under a minute
- Built to be trusted, not just used
- CSV import, for the history a live API can't reach
- GitHub Copilot support
- OpenCode: local-only, no API key needed
- Codex CLI: local-only, no API key needed
- Personal usage mode, for when you don't have admin access
- Session-level cost breakdown
- Commands
- Library API reference
See it in action
npx teamspend-cli --tools cursor,claude-code --before 2026-04-01:2026-04-30 --after 2026-06-01:2026-06-30
Example output (shape shown below; your real numbers come from your own org's API data):
teamspend snapshot -- migration cost comparison Tools: cursor -> claude-code
BEFORE (cursor) Total spend: $2,140.00 (exact, usage-based) Active users: 14
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add teamspend -- uvx teamspend-cli
Teamspend: common questions
- Is Teamspend MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Teamspend safety report
- How do I install Teamspend?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Teamspend need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Teamspend maintained?
- The last commit was 11 days ago (2026-09-13). The latest release is v0.2.6.