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