spend_limit_set — Zambo MCP Tool
spend_limit_set
(spend limit set) is one of 37 tools on the
Zambo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call spend_limit_set from your client
- Claude Code Zambo spend_limit_set run in your project directory
- Claude Desktop Zambo spend_limit_set ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Zambo spend_limit_set ~/.cursor/mcp.json
- VS Code Zambo spend_limit_set .vscode/mcp.json
- Zed Zambo spend_limit_set ~/.config/zed/settings.json
- Windsurf Zambo spend_limit_set ~/.codeium/windsurf/mcp_config.json
- Cline Zambo spend_limit_set ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Zambo spend_limit_set ~/.gemini/settings.json
- Grok Zambo spend_limit_set .mcp.json (in your project root)
- ChatGPT Zambo spend_limit_set Settings → Connectors → Advanced → Developer mode
- Claude.ai Zambo spend_limit_set Settings → Connectors → Add custom connector
- LangChain Zambo spend_limit_set pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http zambo https://zambo.dev/mcpOther tools on this server
- capability_search
- memory_recall
- memory_remember
- scam_check
- day_pass_redeem
- spend_limit_status
- handover_accept
- handover
- handover_status
- handover_list
- zambo_home
- activity_today
- workflow_close
- workflow_seal
- zambo_universal
- new_session
- continuity_get_recent
- continuity_list_threads
- continuity_open_thread
- continuity_start_thread
- continuity_set_prefs
- journal_log
- live_price
- pdf_extract
- doc_intel
- leadsignal
- provibe_audit
- ghost_audit_site
- ghost_audit_status
- ghost_audit_report
- credithunt
- prompt_shield
- day_pass_checkout_link
- day_pass_activate
- day_pass_status
- pass_status
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.