MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"autumn": {
"url": "https://autumn.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"autumn": {
"type": "http",
"url": "https://autumn.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Autumn API key.
Find it in the Autumn dashboard → Developer → API keys (looks like am_sk_live_… / am_sk_test_…). Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Autumn API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Autumn connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
get_customer | read | Get a customer Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get. |
list_customers | read | List customers List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }. |
check | read | Check feature access / balance 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. |
list_invoices | read | List invoices List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }. |
get_entity | read | Get an entity Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get. |
list_entities | read | List entities List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }. |
list_features | read | List features List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }. |
get_feature | read | Get a feature Fetch a single feature by id. Autumn API: POST /v1/features.get. |
list_plans | read | List plans List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }. |
get_plan | read | Get a plan Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get. |
preview_attach | read | Preview attaching a plan 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. |
autumn_request | read | Raw read request 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}. |
get_or_create_customer | write | Get or create a customer MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create. |
update_customer | write | Update a customer MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update. |
track_usage | write | Track usage 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. |
attach_plan | write | Attach a plan 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 }. |
create_entity | write | Create an entity MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create. |
open_customer_portal | write | Open customer billing portal 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 }. |
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_request_feature | Request a missing feature Tell usefulapi that the user needs something the Autumn tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. 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. Does not count against the meter. | |
autumn_cancel_subscription | Cancel the Pro subscription Cancel the caller's Autumn Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run autumn_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Autumn server only. Subscribe with autumn_upgrade (it returns a Stripe Checkout link). Cancel any time with autumn_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running autumn_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Autumn. The server calls the Autumn API with your own Autumn access, so it sees only the data that your account can see.
The login page asks for your Autumn API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Autumn API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Autumn API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Autumn.
Yes, if you approve it. 6 of the 18 Autumn tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Autumn server only. Run autumn_usage_status to see how many calls you used.
Ask the AI to run autumn_upgrade: it returns a Stripe Checkout link. To cancel, run autumn_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with autumn_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
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.