[ docs ]MCP · CLI
Claude Code
One command. OAuth by default; a header for CI and containers.
Setup
Add the server. Run /mcp inside a session to complete the login.
Terminalclaude mcp add --transport http zomler https://api.zomler.com/mcpFor CI, a container or a shared machine, pass a key and there is no login step.
Terminal, with a keyclaude mcp add --transport http zomler https://api.zomler.com/mcp \ --header "Authorization: Bearer zk_live_…"Scope it to a project with --scope project to check the config into .mcp.json for the team. Keep keys out of that file; use the OAuth form there.
What you get
One tool per platform, plus capabilities and check_balance, at https://api.zomler.com/mcp. Every answer is the envelope: what was measured, when, what was left out and why, and what it cost. Fresh fetches spend credits; anything already held is free.
Keys are created under API keys in the dashboard, where each one's calls and spend are listed. Revoking a key stops this client on its next call. The same key also calls the REST API.