autumn
Server Details
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
- 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
18 toolsattach_planAttach a planDestructiveInspect
MUTATES Autumn billing data — attaches (subscribes) a plan to a customer; may create an invoice / return a payment URL. Autumn API: POST /v1/billing.attach. Returns { customer_id, invoice, payment_url, required_action }.
| Name | Required | Description | Default |
|---|---|---|---|
| plan_id | Yes | The ID of the plan. | |
| version | No | The version of the plan to attach. | |
| customize | No | Optional plan overrides (price, items, licenses, free trial). | |
| entity_id | No | The ID of the entity to attach the plan to. | |
| customer_id | Yes | The ID of the customer to attach the plan to. | |
| success_url | No | URL to redirect to after a successful checkout. | |
| invoice_mode | No | Invoice-mode configuration object (send an invoice instead of auto-charging). | |
| redirect_mode | No | Checkout redirect mode: always, if_required, or never. | |
| feature_quantities | No | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. | |
| checkout_session_params | No | Extra Stripe checkout session params (can carry metadata). |
autumn_requestRaw read requestRead-onlyInspect
Power-user escape hatch: POST to any Autumn read/preview endpoint not wrapped by a dedicated tool. READ-ONLY — the path is validated to only allow .get / .list / .check / .preview_* actions; write actions are rejected. Autumn API: POST {path}.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON body object to POST (the endpoint's params). | |
| path | Yes | Full API path, e.g. "/v1/customers.get". Only read/preview suffixes are allowed. |
checkCheck feature access / balanceRead-onlyInspect
READ-ONLY entitlement check: does a customer have access to (or enough balance of) a feature? Autumn API: POST /v1/balances.check. This tool never records usage — it does not expose send_event or lock.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity id for entity-scoped balances (e.g. per-seat limits). | |
| feature_id | Yes | The ID of the feature to check. | |
| customer_id | Yes | The ID of the customer. | |
| with_preview | No | Include upgrade/upsell (paywall) info in the response when access is denied. | |
| required_balance | No | Minimum balance required for access. Returns allowed:false if below. Defaults to 1. |
create_entityCreate an entityDestructiveInspect
MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The name of the entity. | |
| entity_id | Yes | The ID of the entity. | |
| feature_id | Yes | The ID of the feature this entity is associated with. | |
| customer_id | Yes | The ID of the customer to create the entity for. | |
| billing_controls | No | Optional billing controls for the entity (spend/usage limits). |
get_customerGet a customerRead-onlyInspect
Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. | |
| customer_id | Yes | Your unique identifier for the customer. |
get_entityGet an entityRead-onlyInspect
Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. | |
| entity_id | Yes | The ID of the entity. | |
| customer_id | Yes | The ID of the customer that owns the entity. |
get_featureGet a featureRead-onlyInspect
Fetch a single feature by id. Autumn API: POST /v1/features.get.
| Name | Required | Description | Default |
|---|---|---|---|
| feature_id | Yes | The ID of the feature. |
get_or_create_customerGet or create a customerDestructiveInspect
MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Customer's name. | |
| No | Customer's email address. | ||
| expand | No | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. | |
| currency | No | Currency to bill this customer in (e.g. usd, eur). | |
| metadata | No | Arbitrary key/value metadata for the customer. | |
| stripe_id | No | Existing Stripe customer id, if any. | |
| customer_id | Yes | Your unique identifier for the customer (null to create an anonymous customer). | |
| fingerprint | No | Unique identifier to detect duplicate customers / prevent free-trial abuse. | |
| create_in_stripe | No | Whether to create the customer in Stripe. |
get_planGet a planRead-onlyInspect
Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
| Name | Required | Description | Default |
|---|---|---|---|
| plan_id | Yes | The ID of the plan to retrieve. | |
| version | No | The plan version to get. Defaults to the latest. |
list_customersList customersRead-onlyInspect
List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, 1-5000. Default 50. | |
| plans | No | Filter by plan: array of { id, versions? } objects. | |
| search | No | Search customers by id, name, or email. | |
| processors | No | Filter by processor type: stripe, revenuecat, vercel. | |
| start_cursor | No | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). | |
| subscription_status | No | Filter by status: "active" or "scheduled". Defaults to both. |
list_entitiesList entitiesRead-onlyInspect
List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, 1-5000. Default 50. | |
| plans | No | Filter by plan: array of { id, versions? } objects. | |
| search | No | Search entities by id or name. | |
| processors | No | Filter by parent customer processor: stripe, revenuecat, vercel. | |
| customer_id | Yes | Restrict the response to entities owned by this customer id. | |
| start_cursor | No | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). | |
| subscription_status | No | Filter by status: "active" or "scheduled". Defaults to both. |
list_featuresList featuresRead-onlyInspect
List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_invoicesList invoicesRead-onlyInspect
List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, 1-5000. Default 50. | |
| status | No | Filter by invoice status: draft, open, paid, void, uncollectible. | |
| entity_id | No | Filter to a single entity by id (must be paired with customer_id). | |
| customer_id | No | Filter to a single customer by id. | |
| start_cursor | No | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). | |
| processor_types | No | Filter by processor: stripe, revenuecat. |
list_plansList plansRead-onlyInspect
List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | No | Entity id for entity-scoped plans. | |
| customer_id | No | Include eligibility info (trial availability, attach scenario) for this customer. | |
| all_versions | No | If true, include all plan versions. | |
| include_archived | No | If true, include archived plans. |
open_customer_portalOpen customer billing portalDestructiveInspect
MUTATES Autumn billing data — creates a Stripe billing-portal session for a customer to manage their subscription. Autumn API: POST /v1/billing.open_customer_portal. Returns { customer_id, url }.
| Name | Required | Description | Default |
|---|---|---|---|
| return_url | No | URL to redirect to when the back button is clicked in the portal. | |
| customer_id | Yes | The ID of the customer to open the billing portal for. | |
| configuration_id | No | Stripe billing-portal configuration id. |
preview_attachPreview attaching a planRead-onlyInspect
Preview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything. Read-only. Autumn API: POST /v1/billing.preview_attach.
| Name | Required | Description | Default |
|---|---|---|---|
| plan_id | Yes | The ID of the plan. | |
| version | No | The version of the plan to attach. | |
| customize | No | Optional plan overrides (price, items, licenses, free trial). | |
| entity_id | No | The ID of the entity to attach the plan to. | |
| customer_id | Yes | The ID of the customer to attach the plan to. | |
| feature_quantities | No | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. |
track_usageTrack usageDestructiveInspect
MUTATES Autumn billing data — records a usage event (deducts/credits a feature balance). Provide EITHER feature_id OR event_name. Autumn API: POST /v1/balances.track.
| Name | Required | Description | Default |
|---|---|---|---|
| value | No | Amount of usage to record. Defaults to 1. Negative values credit the balance. | |
| entity_id | No | Entity id for entity-scoped balances. | |
| timestamp | No | Unix timestamp (ms) for the event. Defaults to now. | |
| event_name | No | Event name to track usage for. Provide this OR feature_id. | |
| feature_id | No | The feature to track usage for. Provide this OR event_name. | |
| properties | No | Additional properties to attach to the usage event. | |
| customer_id | Yes | The ID of the customer. | |
| idempotencyKey | No | Optional key to dedupe retried events. |
update_customerUpdate a customerDestructiveInspect
MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Customer's name. | |
| No | Customer's email address. | ||
| currency | No | Currency to bill this customer in (e.g. usd, eur). | |
| metadata | No | Arbitrary key/value metadata for the customer. | |
| stripe_id | No | Stripe customer id. | |
| customer_id | Yes | ID of the customer to update. | |
| fingerprint | No | Duplicate-detection fingerprint. | |
| new_customer_id | No | New id for the customer. |
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!