Staxy ships an official MCP server: the @staxy/mcp npm package. Connect it to Claude, Cursor or any MCP-capable client, and your AI agent can read and manage the catalogue for you: list what renews this week, record a payment, file new servers under the right project, retag half the fleet in one go.
1. Create an API key
In the Staxy app open Settings, then API keys and create a key.
- The key looks like
stx_...and is shown only once — copy it right away. - Pick the scope: read-only lets the agent look things up; read and write also lets it create and change data.
- The key acts on your behalf. Treat it like a password, and revoke it in the same screen if it ever leaks — revocation applies on the next request.
2. Add the server to your client
You need Node.js 20 or newer (npx comes with it).
Claude Code — one command:
claude mcp add staxy -e STAXY_API_KEY=stx_... -- npx -y @staxy/mcp
Claude Desktop, Cursor and other JSON-configured clients:
{
"mcpServers": {
"staxy": {
"command": "npx",
"args": ["-y", "@staxy/mcp"],
"env": { "STAXY_API_KEY": "stx_..." }
}
}
}
In Claude Desktop the file is claude_desktop_config.json (Settings, Developer, Edit config). In Cursor it is Settings, MCP, Add new global MCP server.
Restart the client and the staxy server appears with its tools.
3. What the agent can do
The server exposes 28 tools over your account:
- Look things up: projects, units with all their details, providers, payment history, monthly spend trend, global search.
- Answer the main question:
upcoming_renewalsreturns everything due within a horizon you choose, sorted by date, with totals per currency. - Manage the catalogue: create and edit projects, units and providers, move units between projects, retag in bulk, duplicate units.
- Keep the ledger honest: mark renewals as paid, postpone a renewal date, edit or delete payment records.
Prompts that work well:
- "What renews in the next two weeks and how much will it cost?"
- "Add a Hetzner VPS called build-runner-2, 20 euros a month, next payment on the 1st."
- "Move every unit tagged legacy into the Archive project."
- "I just paid for staxy.app at Namecheap — record it."
Security notes
- Everything the agent does goes through the same API as the app: your plan limits, validation and rate limits all apply.
- A read-only key cannot change anything — the server rejects every mutation with it.
- Vault secrets (passwords, SSH keys) are never available through MCP, regardless of scope.
- Revoking a key in Settings cuts its access immediately.
Troubleshooting
- 401 errors: the key was revoked, expired or mistyped. Create a fresh one and update
STAXY_API_KEY. - "This API key is read-only": the agent tried to change data with a read-only key. Create a read and write key if that was intended.
- Self-hosted or staging: point the server elsewhere with the
STAXY_API_URLenvironment variable.