Amberflo MCP by usefulapi is an MCP server with 14 tools an agent can call, among them amberflo_assign_customer_plan, amberflo_create_customer, amberflo_explain_usage. It answers at https://amberflo.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
amberflo_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. Inputs: customer_id, product_plan_id, product_id, start_time_in_seconds, end_time_in_seconds |
amberflo_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/. Inputs: customer_id, customer_name, customer_email, enabled, traits, create_in_stripe |
amberflo_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. Inputs: meter_api_name, start_time_in_seconds, end_time_in_seconds, take_limit, group_by, filter |
amberflo_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. Inputs: start_time_in_seconds, end_time_in_seconds, time_grouping_interval, group_by_customer_id, filter_by_customer_id |
amberflo_get_customer | Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>. Inputs: customer_id |
amberflo_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. Inputs: customer_id, product_id, from_cache, with_payment_status, latest, product_plan_id |
amberflo_get_customer_plan | Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>. Inputs: customer_id |
amberflo_get_usage | Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/. Inputs: meter_api_name, aggregation, time_grouping_interval, start_time_in_seconds, end_time_in_seconds, group_by |
amberflo_ingest_usage | 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. Inputs: meter_api_name, meter_value, meter_time_in_millis, customer_id, dimensions, unique_id |
amberflo_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. Inputs: customer_id, product_id, from_cache, with_payment_status |
amberflo_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>. Inputs: customer_id |
amberflo_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_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_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>. Inputs: customer_id, product_id |
Every block below points at https://amberflo.usefulapi.io/mcp. Pick your client and copy.
claude mcp add --transport http amberflo-mcp-by-usefulapi https://amberflo.usefulapi.io/mcp
{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://amberflo.usefulapi.io/mcp"]
}
}
}{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"servers": {
"amberflo-mcp-by-usefulapi": {
"type": "http",
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"context_servers": {
"amberflo-mcp-by-usefulapi": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"serverUrl": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}name: Amberflo MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
- name: Amberflo MCP by usefulapi
type: streamable-http
url: https://amberflo.usefulapi.io/mcp{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"httpUrl": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"type": "http",
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"amberflo-mcp-by-usefulapi": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Famberflo.usefulapi.io%2Fmcp&type=streamable_http&id=amberflo-mcp-by-usefulapi&name=Amberflo%20MCP%20by%20usefulapi
It answered our last check on 24 October 2026 in 375 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by usefulapi.io and served from amberflo.usefulapi.io, the vendor's own domain: https://amberflo.usefulapi.io/mcp.
14, as returned by the server's own tools/list on 22 September 2026: amberflo_assign_customer_plan, amberflo_create_customer, amberflo_explain_usage, amberflo_get_all_usage, amberflo_get_customer, amberflo_get_customer_invoice, amberflo_get_customer_plan, amberflo_get_usage, and 6 more.
It answered our last check on 24 October 2026 in 375 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://amberflo.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.usefulapi. Endpoint host: amberflo.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:amberflo.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.