run_sandbox_scenario — Spoolis MCP Tool Mutating
run_sandbox_scenario
(run sandbox scenario) is one of 32 tools on the
Spoolis
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_sandbox_scenario from your client
- Claude Code Spoolis run_sandbox_scenario run in your project directory
- Claude Desktop Spoolis run_sandbox_scenario ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Spoolis run_sandbox_scenario ~/.cursor/mcp.json
- VS Code Spoolis run_sandbox_scenario .vscode/mcp.json
- Zed Spoolis run_sandbox_scenario ~/.config/zed/settings.json
- Windsurf Spoolis run_sandbox_scenario ~/.codeium/windsurf/mcp_config.json
- Cline Spoolis run_sandbox_scenario ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Spoolis run_sandbox_scenario ~/.gemini/settings.json
- Grok Spoolis run_sandbox_scenario .mcp.json (in your project root)
- ChatGPT Spoolis run_sandbox_scenario Settings → Connectors → Advanced → Developer mode
- Claude.ai Spoolis run_sandbox_scenario Settings → Connectors → Add custom connector
- LangChain Spoolis run_sandbox_scenario pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://spoolis.com/api/mcpOther tools on this server
- verify_result
- compile_spool
- create_spool
- get_spool
- get_receipt_status
- request_review
- get_review
- decide_review
- open_dispute
- get_dispute
- list_discrepancies
- open_discrepancy
- resolve_discrepancy
- list_sources
- add_source
- sync_source
- list_facts
- run_matching
- list_matches
- create_counterparty_invite
- propose_spool
- accept_spool
- amend_spool
- abandon_spool
- decline_spool
- cancel_spool
- commit_payment
- submit_evidence
- verify_spool
- complete_spool
- get_spool_events
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.