amberflo_assign_customer_plan — amberflo MCP Tool
amberflo_assign_customer_plan
(amberflo assign customer plan) is one of 14 tools on the
amberflo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call amberflo_assign_customer_plan from your client
- Claude Code amberflo amberflo_assign_customer_plan run in your project directory
- Claude Desktop amberflo amberflo_assign_customer_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor amberflo amberflo_assign_customer_plan ~/.cursor/mcp.json
- VS Code amberflo amberflo_assign_customer_plan .vscode/mcp.json
- Zed amberflo amberflo_assign_customer_plan ~/.config/zed/settings.json
- Windsurf amberflo amberflo_assign_customer_plan ~/.codeium/windsurf/mcp_config.json
- Cline amberflo amberflo_assign_customer_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI amberflo amberflo_assign_customer_plan ~/.gemini/settings.json
- Grok amberflo amberflo_assign_customer_plan .mcp.json (in your project root)
- ChatGPT amberflo amberflo_assign_customer_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai amberflo amberflo_assign_customer_plan Settings → Connectors → Add custom connector
- LangChain amberflo amberflo_assign_customer_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http amberflo https://amberflo.usefulapi.io/mcp
Other tools on this server
- amberflo_list_customers
- amberflo_get_customer
- amberflo_list_meters
- amberflo_get_usage
- amberflo_get_all_usage
- amberflo_explain_usage
- amberflo_get_customer_plan
- amberflo_list_customer_plan_history
- amberflo_list_customer_invoices
- amberflo_get_customer_invoice
- amberflo_list_prepaid_orders
- amberflo_create_customer
- amberflo_ingest_usage
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.