estimate_simulation_size_and_cost — Neumann MCP Tool
estimate_simulation_size_and_cost
(estimate simulation size and cost) is one of 17 tools on the
Neumann
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call estimate_simulation_size_and_cost from your client
- Claude Code Neumann estimate_simulation_size_and_cost run in your project directory
- Claude Desktop Neumann estimate_simulation_size_and_cost ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Neumann estimate_simulation_size_and_cost ~/.cursor/mcp.json
- VS Code Neumann estimate_simulation_size_and_cost .vscode/mcp.json
- Zed Neumann estimate_simulation_size_and_cost ~/.config/zed/settings.json
- Windsurf Neumann estimate_simulation_size_and_cost ~/.codeium/windsurf/mcp_config.json
- Cline Neumann estimate_simulation_size_and_cost ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Neumann estimate_simulation_size_and_cost ~/.gemini/settings.json
- Grok Neumann estimate_simulation_size_and_cost .mcp.json (in your project root)
- ChatGPT Neumann estimate_simulation_size_and_cost Settings → Connectors → Advanced → Developer mode
- Claude.ai Neumann estimate_simulation_size_and_cost Settings → Connectors → Add custom connector
- LangChain Neumann estimate_simulation_size_and_cost pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http neumann https://neumann.kromatic.com/mcp
Other tools on this server
- run_monte_carlo_simulation
- rank_inputs_by_impact
- summarize_outcome_scenarios
- check_simulation_model
- convert_range_to_distribution
- convert_distribution_to_range
- get_simulation_results
- check_account_and_credits
- send_feedback
- buy_credits
- create_result_share_link
- save_graph
- list_graphs
- get_graph
- delete_graph
- delete_run
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.