Connect-MCP

Autumn MCP by usefulapi

io.usefulapi/autumn · v1.11.1

MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.

MCPremoteno credentialsCRM & salesFinance

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 18 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 18 tools · 13 read, 5 write (incl. delete/pay) · CRM & sales, Finance

Test call list_customers: needs a key: HTTP 401 (757 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://autumn.usefulapi.io/mcp

Tools

18 tools listed at last check
  • get_customer Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
  • list_customers List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
  • check 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 List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
  • get_entity Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
  • 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 List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
  • get_feature Fetch a single feature by id. Autumn API: POST /v1/features.get.
  • list_plans List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
  • get_plan Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
  • preview_attach 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 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 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 MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
  • 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 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 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 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 }.

Badge

Connect-MCP badge for io.usefulapi/autumn

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/autumn.svg)](https://clawy.uk/mcp/s/io.usefulapi/autumn)

Repository · Website