orb_get_customer_costs — orb MCP Tool
orb_get_customer_costs
(orb get customer costs) is one of 26 tools on the
orb
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call orb_get_customer_costs from your client
- Claude Code orb orb_get_customer_costs run in your project directory
- Claude Desktop orb orb_get_customer_costs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor orb orb_get_customer_costs ~/.cursor/mcp.json
- VS Code orb orb_get_customer_costs .vscode/mcp.json
- Zed orb orb_get_customer_costs ~/.config/zed/settings.json
- Windsurf orb orb_get_customer_costs ~/.codeium/windsurf/mcp_config.json
- Cline orb orb_get_customer_costs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI orb orb_get_customer_costs ~/.gemini/settings.json
- Grok orb orb_get_customer_costs .mcp.json (in your project root)
- ChatGPT orb orb_get_customer_costs Settings → Connectors → Advanced → Developer mode
- Claude.ai orb orb_get_customer_costs Settings → Connectors → Add custom connector
- LangChain orb orb_get_customer_costs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http orb https://orb.usefulapi.io/mcpOther tools on this server
- orb_ping
- orb_list_customers
- orb_get_customer
- orb_get_customer_by_external_id
- orb_get_customer_credits
- orb_get_customer_credits_ledger
- orb_list_plans
- orb_get_plan
- orb_list_subscriptions
- orb_get_subscription
- orb_get_subscription_costs
- orb_get_subscription_usage
- orb_get_subscription_schedule
- orb_list_invoices
- orb_get_invoice
- orb_get_upcoming_invoice
- orb_list_items
- orb_get_item
- orb_list_prices
- orb_get_price
- orb_list_metrics
- orb_list_coupons
- orb_list_alerts
- orb_create_customer
- orb_update_customer
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.