Autumn MCP server. MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
Add to your MCP config, then reload & authorize:
{
"mcpServers": {
"autumn": {
"url": "https://autumn.usefulapi.io/mcp"
}
}
}| Tool | Type | What it does |
|---|---|---|
autumn_get_customer | read | Get customer Fetch a single Autumn customer by id, optionally expanding related data such as invoices, entities, subscriptions and feature balances. |
autumn_list_customers | read | List customers List and filter customers with cursor pagination, narrowing by plan, subscription status, processor or a free-text search over id, name and email. |
autumn_check | read | Check Run a read-only entitlement check to see whether a customer has access to (or enough balance of) a feature, optionally including paywall/upsell preview info. |
autumn_list_invoices | read | List invoices List invoices with cursor pagination, filtering by customer, entity, invoice status (draft/open/paid/void) or payment processor. |
autumn_get_entity | read | Get entity Fetch a single entity (for example a seat) belonging to a customer, optionally expanding its related billing data. |
autumn_list_entities | read | List entities List a customer's entities with cursor pagination and filters by plan, subscription status, processor or a search over id and name. |
autumn_list_features | read | List features List every feature defined in the current Autumn environment so you know which features the balance and usage tools can target. |
autumn_get_feature | read | Get feature Fetch a single feature by its id, returning that feature's full definition. |
autumn_list_plans | read | List plans List all plans (products) in the environment, optionally including per-customer eligibility, archived plans or every plan version. |
autumn_get_plan | read | Get plan Fetch a single plan by id, optionally pinned to a specific version instead of the latest. |
autumn_preview_attach | read | Preview attach Preview the cost and effect of attaching a plan to a customer without charging or changing anything — a safe dry run before autumn_attach_plan. |
autumn_request | read | Request Power-user read escape hatch that POSTs to any Autumn .get/.list/.check/.preview_* endpoint not covered by a dedicated tool, with write paths rejected before any request is sent. |
autumn_get_or_create_customer | write | Get or create customer Fetch a customer by id, creating them (optionally in Stripe too) if they do not yet exist in Autumn. |
autumn_update_customer | write | Update customer Partially update a customer's name, email, fingerprint, metadata, Stripe id, currency or id — only the fields you provide change. |
autumn_track_usage | write | Track usage Record a usage event that deducts or credits a customer's feature balance, addressed by either feature_id or event_name. |
autumn_attach_plan | write | Attach plan Attach (subscribe) a plan to a customer, which may create an invoice or return a Stripe payment URL for checkout. |
autumn_create_entity | write | Create entity Create an entity (for example a seat) under a customer and tie it to a feature, with optional per-entity billing controls. |
autumn_open_customer_portal | write | Open customer portal Create a Stripe billing-portal session so a customer can manage their own subscription, returning the portal URL. |
autumn_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. | |
autumn_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Autumn 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. Read-only; does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
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.