update_billing_settings — Last Price MCP Tool Mutating
update_billing_settings
(update billing settings) is one of 21 tools on the
Last Price
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call update_billing_settings from your client
- Claude Code Last Price update_billing_settings run in your project directory
- Claude Desktop Last Price update_billing_settings ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Last Price update_billing_settings ~/.cursor/mcp.json
- VS Code Last Price update_billing_settings .vscode/mcp.json
- Zed Last Price update_billing_settings ~/.config/zed/settings.json
- Windsurf Last Price update_billing_settings ~/.codeium/windsurf/mcp_config.json
- Cline Last Price update_billing_settings ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Last Price update_billing_settings ~/.gemini/settings.json
- Grok Last Price update_billing_settings .mcp.json (in your project root)
- ChatGPT Last Price update_billing_settings Settings → Connectors → Advanced → Developer mode
- Claude.ai Last Price update_billing_settings Settings → Connectors → Add custom connector
- LangChain Last Price update_billing_settings pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pricing https://api.last-price.ai/api/mcp/rpcOther tools on this server
- pricing_conversation
- compute_price
- verify_price
- list_functions
- browse_catalog
- report_outcome
- get_price_guardrails
- set_price_guardrails
- get_pricing_analysis
- get_function
- update_function
- get_billing_settings
- list_outcomes
- get_usage
- list_usage_events
- get_receipt
- list_receipts
- list_notifications
- mark_notifications_read
- read_my_inbox
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 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.