Lago MCP server

What the model can do

Lago usage-based billing (Cloud or self-hosted): customers, invoices with payment state, subscriptions, plans, payments, credit notes and a customer's current usage. Can create, change or delete a customer, send usage events, issue one-off invoices, finalize, void, refresh, retry, update or delete draft invoices, record payments and send payment requests, retry payments, issue or void credit notes, create, change and delete plans, create add-ons and billable metrics, create, change, apply and delete coupons, create, top up and terminate wallets, and start, change or cancel subscriptions.

Reads

• lago_list_customersLago customers: your external id, name, legal name, email, website, country, currency, created and updated.
• lago_list_invoicesLago invoices: number, customer, type, status (draft, finalized, voided, failed), payment status (pending, succeeded, failed), overdue…
• lago_list_subscriptionsLago subscriptions: external id, customer, plan code, status, billing time, start, end and termination…
• lago_list_plansLago plans: code, name, interval, base amount and currency, trial days, whether paid in advance, how many usage charges.
• lago_list_paymentsPayments recorded in Lago: amount, currency, status, type, reference, the invoices they paid, and when.
• lago_list_credit_notesLago credit notes: number, invoice, issue date, reason, credit and refund status, totals.
• lago_current_usageA customer's usage so far in the current billing period of one subscription: the period, the amount so far and each charge's units and amount.
• lago_get_invoiceOne Lago invoice by its lago_id, with its fees (fee lago_id, item, units, amounts): the fee ids are what lago_create_credit_note takes.

Acts, when you ask

These change something in Lago. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• lago_create_customerCreates a Lago customer with your external id and a name, and optionally a legal name, email and website.
• lago_send_usage_eventMOVES MONEY.
• lago_delete_customerDESTRUCTIVE, MOVES MONEY.
• lago_finalize_invoiceMOVES MONEY.
• lago_void_invoiceDESTRUCTIVE, MOVES MONEY.
• lago_refresh_invoiceRecalculates a DRAFT Lago invoice from the usage and charges recorded so far, replacing its amounts.
• lago_retry_invoiceMOVES MONEY.
• lago_retry_invoice_paymentMOVES MONEY.
• lago_create_credit_noteMOVES MONEY.
• lago_create_couponCreates a Lago coupon (a discount definition): a name and code, fixed amount (cents and currency) or percentage, frequency (once…
• lago_apply_couponMOVES MONEY.
• lago_create_walletMOVES MONEY.
• lago_top_up_walletMOVES MONEY.
• lago_create_subscriptionMOVES MONEY.
• lago_cancel_subscriptionDESTRUCTIVE, MOVES MONEY.
• lago_update_customerOVERWRITES.
• lago_update_subscriptionMOVES MONEY.
• lago_create_one_off_invoiceMOVES MONEY.
• lago_update_invoiceSets a Lago invoice's payment status (pending, succeeded, failed) or adds or changes metadata key-values on it (at most 5…
• lago_delete_draft_invoiceDESTRUCTIVE.
• lago_create_paymentMOVES MONEY.
• lago_create_payment_requestSENDS, MOVES MONEY.
• lago_create_planCreates a Lago plan: name, code, billing interval, base amount in cents and currency, whether the base is paid in advance…
• lago_update_planMOVES MONEY.
• lago_delete_planDESTRUCTIVE.
• lago_create_add_onCreates a Lago add-on (a one-off item for one-off invoices): name, code, amount in cents and currency, optional description and invoice display name.
• lago_create_billable_metricCreates a Lago billable metric (what usage events are counted and how): name, code (events send it), aggregation (count, sum, max, unique count…
• lago_update_couponChanges a Lago coupon by code: name, description, expiry, and (only while it has never been applied) its amount, rate or reusability; once applied…
• lago_delete_couponDESTRUCTIVE.
• lago_terminate_walletDESTRUCTIVE, MOVES MONEY.
• lago_void_credit_noteDESTRUCTIVE, MOVES MONEY.

Connect it

First connect Lago on Dashboard → Connections, then add Memtro to your client once. The Lago tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Lago connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which invoices are overdue, and for how much?
• › How much usage has Acme run up this billing period?
• › Which customers are on the Growth plan?
• › Issue a credit note for the duplicated fee on the Brightwave Ltd invoice
• › Send Northwind a payment request for their two overdue invoices

Questions

Is this an official Lago MCP server?

No. It is Memtro's MCP server with Memtro's Lago connector behind it: the connector reads Lago through its API with the credentials you connect on Dashboard → Connections, and Lago publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Lago?

Only when you ask, and only what it has been granted: create a customer when no customer has that external id; overwrite a customer's name, legal name, email or website; send a billable usage event to a subscription; delete a customer, terminating their subscriptions; finalize a draft invoice (numbers it, may email and charge the customer); void an invoice, optionally with a credit note and refund; refresh a draft invoice's amounts; retry generating a failed invoice; retry collecting payment on an invoice; issue a credit note on an invoice (credit, refund or offset); create a coupon; apply a coupon to a customer; create a prepaid-credit wallet for a customer; top up a wallet with paid or granted credits; subscribe a customer to a plan; cancel (terminate) a subscription; change a subscription's name, end date or plan overrides; issue a one-off invoice for add-ons (not sent for payment unless asked); record a manual payment on an invoice; email a customer a payment request for overdue invoices; set an invoice's payment status or metadata; delete a draft invoice permanently; create a plan; change a plan's name, price or trial (affects its subscribers); delete a plan with no subscriptions; create an add-on; create a billable metric; change a coupon; delete a coupon; terminate a wallet; void the remaining credit of a credit note. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Finance and commerce

• Xero MCP server
• Stripe MCP server
• Felloh MCP server
• Wise MCP server
• Starling Bank MCP server
• QuickBooks Online MCP server