Amberflo MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.

Deletes · 3

Compare Registry entry

14 tools: 3 can delete or cancel things and 11 only read.

Scanned Oct 21, 2026

Deletes or cancels3Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads11Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http amberflo https://amberflo.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

14 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

amberflo_assign_customer_planWRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed.No findings
Why it is in this group
- The name "amberflo_assign_customer_plan" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.
Annotations the server declares
- title: Assign customer plan
- destructiveHint: true
amberflo_create_customerWRITE: create/register a new customer in Amberflo (id + name required; optional email, enabled flag, and traits).No findings
Why it is in this group
- The name "amberflo_create_customer" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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/.
Annotations the server declares
- title: Create customer
- destructiveHint: true
amberflo_ingest_usageWRITE: record/ingest a single usage meter event (writes billable usage data) to the Amberflo ingestion host.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Ingest usage event
- destructiveHint: true

Only reads 11Looks things up and changes nothing.Claude Code: allow

amberflo_explain_usageExplain/drill into the raw meter events behind a meter's usage over a time range — useful to debug why a number looks off.No findings
Why it is in this group
- The name "amberflo_explain_usage" says "explain": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Explain usage
- readOnlyHint: true
amberflo_get_all_usageGet total usage across all meters over a time range, optionally grouped by customer or filtered to one customer.No findings
Why it is in this group
- The name "amberflo_get_all_usage" says "get": a word for reading.
Description, as the server wrote it
Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.
Annotations the server declares
- title: Get all usage
- readOnlyHint: true
amberflo_get_customerFetch a single customer by its Amberflo customerId.No findings
Why it is in this group
- The name "amberflo_get_customer" says "get": a word for reading.
Description, as the server wrote it
Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.
Annotations the server declares
- title: Get a customer
- readOnlyHint: true
amberflo_get_customer_invoiceGet a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day.No findings
Why it is in this group
- The name "amberflo_get_customer_invoice" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Get customer invoice
- readOnlyHint: true
amberflo_get_customer_planGet a customer's LATEST assigned product plan (pricing).No findings
Why it is in this group
- The name "amberflo_get_customer_plan" says "get": a word for reading.
Description, as the server wrote it
Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.
Annotations the server declares
- title: Get customer plan
- readOnlyHint: true
amberflo_get_usageQuery aggregated usage for a single meter over a time range, optionally grouped/filtered.No findings
Why it is in this group
- The name "amberflo_get_usage" says "get": a word for reading.
Description, as the server wrote it
Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
Annotations the server declares
- title: Query usage for a meter
- readOnlyHint: true
amberflo_list_customer_invoicesList all invoices for a customer (optionally for a specific product), with payment status.No findings
Why it is in this group
- The name "amberflo_list_customer_invoices" says "list": a word for reading.
Description, as the server wrote it
List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.
Annotations the server declares
- title: List customer invoices
- readOnlyHint: true
amberflo_list_customer_plan_historyList the full history of product plans assigned to a customer over time.No findings
Why it is in this group
- The name "amberflo_list_customer_plan_history" says "list": a word for reading.
Description, as the server wrote it
List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>.
Annotations the server declares
- title: List customer plan history
- readOnlyHint: true
amberflo_list_customersList all customers registered in your Amberflo account (id, name, email, traits, enabled).No findings
Why it is in this group
- The name "amberflo_list_customers" says "list": a word for reading.
Description, as the server wrote it
List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.
Annotations the server declares
- title: List customers
- readOnlyHint: true
amberflo_list_metersList all meter definitions in your account (id, meterApiName, label, meterType, aggregation, etc.).No findings
Why it is in this group
- The name "amberflo_list_meters" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List meters
- readOnlyHint: true
amberflo_list_prepaid_ordersList a customer's active prepaid credit orders for a product.No findings
Why it is in this group
- The name "amberflo_list_prepaid_orders" says "list": a word for reading.
Description, as the server wrote it
List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>.
Annotations the server declares
- title: List prepaid orders
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http amberflo https://amberflo.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__amberflo__amberflo_list_customers",
      "mcp__amberflo__amberflo_get_customer",
      "mcp__amberflo__amberflo_list_meters",
      "mcp__amberflo__amberflo_get_usage",
      "mcp__amberflo__amberflo_get_all_usage",
      "mcp__amberflo__amberflo_explain_usage",
      "mcp__amberflo__amberflo_get_customer_plan",
      "mcp__amberflo__amberflo_list_customer_plan_history",
      "mcp__amberflo__amberflo_list_customer_invoices",
      "mcp__amberflo__amberflo_get_customer_invoice",
      "mcp__amberflo__amberflo_list_prepaid_orders"
    ],
    "ask": [],
    "deny": [
      "mcp__amberflo__amberflo_create_customer",
      "mcp__amberflo__amberflo_assign_customer_plan",
      "mcp__amberflo__amberflo_ingest_usage"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as amberflo. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/amberflo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing