Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"amberflo": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"amberflo": {
"type": "http",
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Amberflo API key.
Find it in Amberflo → Settings → API Keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Amberflo API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Amberflo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
amberflo_list_customers | read | List customers List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/. |
amberflo_get_customer | read | Get a customer Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>. |
amberflo_list_meters | read | List meters List all meter definitions in your account (id, meterApiName, label, meterType, aggregation, etc.). Use meterApiName values here as inputs to usage tools. API: GET /meters. |
amberflo_get_usage | read | Query usage for a meter Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/. |
amberflo_get_all_usage | read | Get all usage Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all. |
amberflo_explain_usage | read | Explain usage Explain/drill into the raw meter events behind a meter's usage over a time range — useful to debug why a number looks off. API: POST /usage/explain. |
amberflo_get_customer_plan | read | Get customer plan Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>. |
amberflo_list_customer_plan_history | read | List customer plan history List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>. |
amberflo_list_customer_invoices | read | List customer invoices List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all. |
amberflo_get_customer_invoice | read | Get customer invoice Get a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day. API: GET /payments/billing/customer-product-invoice. |
amberflo_list_prepaid_orders | read | List prepaid orders List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>. |
amberflo_create_customer | write | Create customer WRITE: create/register a new customer in Amberflo (id + name required; optional email, enabled flag, and traits). Optionally auto-create the customer in Stripe. API: POST /customers/. |
amberflo_assign_customer_plan | write | Assign customer plan WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing. |
amberflo_ingest_usage | write | Ingest usage event WRITE: record/ingest a single usage meter event (writes billable usage data) to the Amberflo ingestion host. API: POST /ingest/ on the ingest base URL. |
amberflo_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
amberflo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Amberflo tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
amberflo_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Amberflo tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
amberflo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Amberflo Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run amberflo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Amberflo server only. Subscribe with amberflo_upgrade (it returns a Stripe Checkout link). Cancel any time with amberflo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running amberflo_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Amberflo. The server calls the Amberflo API with your own Amberflo access, so it sees only the data that your account can see.
The login page asks for your Amberflo API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Amberflo API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Amberflo API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Amberflo.
Yes, if you approve it. 3 of the 14 Amberflo tools can create or change data. The other 11 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Amberflo server only. Run amberflo_usage_status to see how many calls you used.
Ask the AI to run amberflo_upgrade: it returns a Stripe Checkout link. To cancel, run amberflo_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with amberflo_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.