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