Invoiced MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://invoiced.usefulapi.io/mcp

claude mcp add --transport http invoiced https://invoiced.usefulapi.io/mcp

{
  "mcpServers": {
    "invoiced": {
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "invoiced": {
      "type": "http",
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}

https://invoiced.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• invoiced_list_customers

  List customers (accounts receivable debtors): name, number, email, payment terms, currency, autopay and chasing settings, owner. Filter by open balance, saved payment method, update time or any exact-match column. GET /customers.

• invoiced_get_customer

  One customer by id: contact details, address, terms, currency, autopay, chasing cadence, credit hold/limit, parent customer, metadata. GET /customers/{id}.

• invoiced_get_customer_balance

  A customer's current balance: total outstanding, past due, and available credit, in the customer's currency (or `currency`). GET /customers/{id}/balance.

• invoiced_list_contacts

  List the contacts of one customer: name, title, email, phone, whether primary (copied on communications) and SMS-enabled. GET /customers/{id}/contacts.

• invoiced_list_invoices

  List invoices with number, customer, status (draft, not_sent, sent, viewed, past_due, pending, paid, voided), dates, totals, balance and line items. Filter by customer, paid flag, invoice date range, update time or any exact-match column. GET /invoices.

• invoiced_get_invoice

  One invoice by id: status, dates, payment terms, totals, balance, line items, discounts, taxes, ship-to, payment and PDF links. `expand` replaces ids with full objects (e.g. customer). GET /invoices/{id}.

• invoiced_get_invoice_payment_plan

  The payment plan (installments with dates, amounts and balances, and approval status) attached to an invoice. Errors with 404 when the invoice has none. GET /invoices/{id}/payment_plan.

• invoiced_list_payments

  List payments received: customer, date, amount, unapplied balance, method (check, wire, ACH, card, ...), reference, whether matched or voided. Read only. GET /payments.

• invoiced_get_payment

  One payment by id, including which invoices and credit notes it was applied to (`applied_to`). GET /payments/{id}?include=applied_to.

• invoiced_list_credit_notes

  List credit notes: customer, status (draft, open, paid, closed, voided), totals, remaining balance, line items. GET /credit_notes.

• invoiced_get_credit_note

  One credit note by id with line items, totals and balance. GET /credit_notes/{id}.

• invoiced_list_estimates

  List estimates (quotes): customer, status (draft, not_sent, sent, approved, invoiced, declined, voided), expiration date, deposit, totals, resulting invoice. GET /estimates.

• invoiced_get_estimate

  One estimate by id with line items, totals, deposit and approval state. GET /estimates/{id}.

• invoiced_list_items

  List the item catalog (products and services): id, name, currency, unit cost, type, taxable. Use item ids as `catalog_item` when creating a draft invoice. GET /items.

• invoiced_get_item

  One catalog item by its id (a string such as "delivery"). GET /items/{id}.

• invoiced_list_tax_rates

  List tax rates: id, name, value, whether a percentage, whether inclusive, currency. GET /tax_rates.

• invoiced_list_plans

  List subscription plans: id, name, currency, amount, pricing mode, billing interval, tiers. GET /plans.

• invoiced_get_plan

  One subscription plan by its id (a string). GET /plans/{id}.

• invoiced_list_subscriptions

  List recurring subscriptions: customer, plan, quantity, billing period, status (not_started, active, past_due, finished, canceled), recurring total and MRR, contract renewal. GET /subscriptions.

• invoiced_get_subscription

  One subscription by id with plan, add-ons, billing period, contract terms, recurring total and MRR. GET /subscriptions/{id}.

• invoiced_list_notes

  List collection notes, newest first, for one customer or one invoice (give exactly one), or all notes when neither is given. GET /customers/{id}/notes, /invoices/{id}/notes or /notes.

• invoiced_list_tasks

  List collection tasks (call, letter, email, review): name, action, customer, assignee, due date, whether complete. GET /tasks.

• invoiced_list_events

  The activity feed, newest first: event type (such as invoice.paid, customer.created), time, the object it concerns and who did it. Optionally only the events of one object. GET /events.

• invoiced_create_customer

  WRITE: create a customer in Invoiced. Nothing is sent to anyone and no money moves. Name is required; Invoiced generates the customer number unless given. POST /customers.

• invoiced_create_draft_invoice

  WRITE: create a DRAFT invoice for a customer. It is always created as a draft: it is not issued, not emailed, not charged and cannot trigger AutoPay until a person finalizes it in Invoiced. At least one line item is required. POST /invoices with draft=true.

• invoiced_add_note

  WRITE: add an internal note to a customer or an invoice (give exactly one). Notes are internal; nothing is sent. POST /notes.

• invoiced_create_task

  WRITE: create a collection task for a customer (a reminder to call, write, email or review). Nothing is sent to the customer. POST /tasks.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 44 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 27 tool descriptions and found no hidden instructions to the AI

Compared with others in Docs, sheets & office worki

• More stars than 0% of the other 2170 servers in this category
• Published to the registry more recently than 96% of the other 2170 servers in this category
• Basic checks equal to or better than 100% of the other 2170 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{