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