amberflo
Server Details
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
14 toolsamberflo_assign_customer_planAssign customer planDestructiveInspect
WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | No | Product id the plan belongs to. | |
| customer_id | Yes | The Amberflo customerId to assign the plan to. | |
| product_plan_id | Yes | The productPlanId of the plan to assign. | |
| end_time_in_seconds | No | When the plan ends, unix epoch seconds. | |
| start_time_in_seconds | No | When the plan takes effect, unix epoch seconds. |
amberflo_create_customerCreate customerDestructiveInspect
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/.
| Name | Required | Description | Default |
|---|---|---|---|
| traits | No | Arbitrary string traits (key/value metadata). | |
| enabled | No | Whether the customer is enabled. | |
| customer_id | Yes | Unique customerId to assign (your identifier for the customer). | |
| customer_name | Yes | Human-readable customer name. | |
| customer_email | No | Customer email address. | |
| create_in_stripe | No | When true, also auto-create this customer in Stripe (adds ?autoCreateCustomerInStripe=true). |
amberflo_explain_usageExplain usageRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | Dimension filter: map of dimension name -> allowed values. | |
| group_by | No | Dimension names to group by, e.g. ["customerId"]. | |
| take_limit | No | Return only the top N records. | |
| aggregation | No | Aggregation function: SUM | COUNT | MIN | MAX. | |
| meter_api_name | Yes | The meterApiName to explain (from amberflo_list_meters). | |
| end_time_in_seconds | No | Range end, unix epoch seconds. Defaults to now if omitted. | |
| start_time_in_seconds | Yes | Range start, unix epoch seconds (inclusive). |
amberflo_get_all_usageGet all usageRead-onlyInspect
Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.
| Name | Required | Description | Default |
|---|---|---|---|
| end_time_in_seconds | No | Range end, unix epoch seconds. Defaults to now if omitted. | |
| group_by_customer_id | No | When true, group results by customer (sends groupBy=customerId). | |
| filter_by_customer_id | No | Restrict results to a single customerId. | |
| start_time_in_seconds | Yes | Range start, unix epoch seconds (inclusive). | |
| time_grouping_interval | Yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
amberflo_get_customerGet a customerRead-onlyInspect
Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The Amberflo customerId to fetch. |
amberflo_get_customer_invoiceGet customer invoiceRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| day | No | Day of month of a specific past invoice. | |
| year | No | Year of a specific past invoice. | |
| month | No | Month (1-12) of a specific past invoice. | |
| latest | No | Fetch the current open invoice. Default true. Ignored when a specific invoice is addressed. | |
| from_cache | No | Use cached invoice (faster). Default true. | |
| product_id | No | Product id. Default "1". | |
| customer_id | Yes | The Amberflo customerId. | |
| product_plan_id | No | Product plan id of a specific past invoice (with year/month/day). | |
| with_payment_status | No | Include payment status. Default true. |
amberflo_get_customer_planGet customer planRead-onlyInspect
Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The Amberflo customerId. |
amberflo_get_usageQuery usage for a meterRead-onlyInspect
Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | Dimension filter: map of dimension name -> allowed values. | |
| group_by | No | Dimension names to group results by, e.g. ["customerId"]. | |
| take_limit | No | Return only the top N groups. | |
| aggregation | Yes | Aggregation function: SUM | COUNT | MIN | MAX. | |
| meter_api_name | Yes | The meterApiName to query (from amberflo_list_meters). | |
| take_is_ascending | No | Sort order for `take` (default false = descending). | |
| end_time_in_seconds | No | Range end, unix epoch seconds. Defaults to now if omitted. | |
| start_time_in_seconds | Yes | Range start, unix epoch seconds (inclusive). | |
| time_grouping_interval | Yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
amberflo_ingest_usageIngest usage eventDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| unique_id | No | Optional idempotency/unique id for the event. | |
| dimensions | No | Optional dimensions (key/value string metadata) for the event. | |
| customer_id | Yes | The customerId this usage belongs to. | |
| meter_value | Yes | The numeric value of the usage event. | |
| meter_api_name | Yes | The meterApiName this event is for. | |
| meter_time_in_millis | Yes | Event timestamp, unix epoch milliseconds. |
amberflo_list_customer_invoicesList customer invoicesRead-onlyInspect
List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.
| Name | Required | Description | Default |
|---|---|---|---|
| from_cache | No | Use cached invoices (faster). Default true. | |
| product_id | No | Product id. Default "1". | |
| customer_id | Yes | The Amberflo customerId. | |
| with_payment_status | No | Include payment status. Default true. |
amberflo_list_customer_plan_historyList customer plan historyRead-onlyInspect
List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The Amberflo customerId. |
amberflo_list_customersList customersRead-onlyInspect
List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
amberflo_list_metersList metersRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
amberflo_list_prepaid_ordersList prepaid ordersRead-onlyInspect
List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=&ProductId=.
| Name | Required | Description | Default |
|---|---|---|---|
| product_id | No | Product id. Default "1". | |
| customer_id | Yes | The Amberflo customerId. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!