issue_envelope — Fleet spend circuit-breaker MCP Tool
issue_envelope
(issue envelope) is one of 6 tools on the
Fleet spend circuit-breaker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call issue_envelope from your client
- Claude Code Fleet spend circuit-breaker issue_envelope run in your project directory
- Claude Desktop Fleet spend circuit-breaker issue_envelope ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fleet spend circuit-breaker issue_envelope ~/.cursor/mcp.json
- VS Code Fleet spend circuit-breaker issue_envelope .vscode/mcp.json
- Zed Fleet spend circuit-breaker issue_envelope ~/.config/zed/settings.json
- Windsurf Fleet spend circuit-breaker issue_envelope ~/.codeium/windsurf/mcp_config.json
- Cline Fleet spend circuit-breaker issue_envelope ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fleet spend circuit-breaker issue_envelope ~/.gemini/settings.json
- Grok Fleet spend circuit-breaker issue_envelope .mcp.json (in your project root)
- ChatGPT Fleet spend circuit-breaker issue_envelope Settings → Connectors → Advanced → Developer mode
- Claude.ai Fleet spend circuit-breaker issue_envelope Settings → Connectors → Add custom connector
- LangChain Fleet spend circuit-breaker issue_envelope pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fleet-spend-circuit-breaker https://textforagents.com/products/fleet-spend-circuit-breaker/mcpOther tools on this server
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.