simulate_cost — ワットク（Wattoku） MCP Tool
simulate_cost
(simulate cost) is one of 11 tools on the
ワットク（Wattoku）
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call simulate_cost from your client
- Claude Code ワットク（Wattoku） simulate_cost run in your project directory
- Claude Desktop ワットク（Wattoku） simulate_cost ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ワットク（Wattoku） simulate_cost ~/.cursor/mcp.json
- VS Code ワットク（Wattoku） simulate_cost .vscode/mcp.json
- Zed ワットク（Wattoku） simulate_cost ~/.config/zed/settings.json
- Windsurf ワットク（Wattoku） simulate_cost ~/.codeium/windsurf/mcp_config.json
- Cline ワットク（Wattoku） simulate_cost ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ワットク（Wattoku） simulate_cost ~/.gemini/settings.json
- Grok ワットク（Wattoku） simulate_cost .mcp.json (in your project root)
- ChatGPT ワットク（Wattoku） simulate_cost Settings → Connectors → Advanced → Developer mode
- Claude.ai ワットク（Wattoku） simulate_cost Settings → Connectors → Add custom connector
- LangChain ワットク（Wattoku） simulate_cost pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wattoku https://wattoku.meliorra.co/api/mcpOther tools on this server
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.