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