Chaser MCP server

What the model can do

Chaser credit control: customers with payer rating and days to pay, invoices with what is owed and overdue, the chasing history on an invoice (reminders sent, notes, promised payment dates, disputes), customer notes and credit-control tasks. Can also add, edit or delete an internal note, create or update a task, pause or resume chasing of an invoice, a customer or the whole organisation, add or change a customer or contact person, and move customers to a chasing schedule — when you ask.

Reads

• chaser_customersCustomers in Chaser (the businesses that owe money): company, main contact and email, status, whether they are being chased, groups…
• chaser_invoicesInvoices in Chaser with customer, status, total, amount due and paid, issue and due dates, promised payment date and whether chasing is on…
• chaser_invoice_historyThe chasing history of one invoice in Chaser: reminders sent (date, type, channel, template), emails (date and subject only), notes, status changes…
• chaser_customer_notesInternal notes on one Chaser customer, with date and type.
• chaser_tasksCredit-control tasks in Chaser: type, category, status, due date, assignee and when done.
• chaser_schedulesChasing schedules in Chaser: id (sch_…), name, how many reminder emails it sends and on which days relative to the due date…
• chaser_contact_personsThe contact persons on one Chaser customer (who reminders can go to besides the main contact): external id, name, email and status.

Acts, when you ask

These change something in Chaser. 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.

• chaser_create_customer_noteAdds an internal note to a customer in Chaser.
• chaser_create_taskCreates an internal credit-control task in Chaser, OPEN, from source manual.
• chaser_pause_chasingPauses Chaser's automatic chasing: of one invoice (e.g. a disputed one), of every invoice of one customer, or of the whole organisation…
• chaser_resume_chasingResumes Chaser's automatic chasing: of one invoice, of every invoice of one customer, or of the whole organisation.
• chaser_update_taskChanges a Chaser credit-control task: complete, cancel, start or reopen it, move its due date, or reassign it to another Chaser user by email…
• chaser_update_customer_noteEdits an internal note on a Chaser customer: its text (replacing the old text) or type.
• chaser_delete_customer_notePermanently deletes an internal note from a Chaser customer.
• chaser_create_customerAdds a customer to Chaser, with the accounting-system id you give (external_id; refused if a customer already has it, so it never overwrites one).
• chaser_update_customerChanges a Chaser customer: company name, main contact's name, email or phone numbers, or archive or reactivate it.
• chaser_add_contact_personAdds a contact person to a Chaser customer, under the id you give (external_id; refused if that customer already has it).
• chaser_update_contact_personChanges a contact person on a Chaser customer: name, email or phone numbers, or archive or reactivate them.
• chaser_delete_contact_personPermanently removes a contact person from a Chaser customer; they stop receiving its reminders.
• chaser_assign_schedulePuts up to 50 Chaser customers on a chasing schedule, which decides which reminders their customers are sent and when (from the next run).

Connect it

First connect Chaser on Dashboard → Connections, then add Memtro to your client once. The Chaser 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 Chaser 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 what has been chased?
• › Has BigCo promised a payment date on their open invoice?
• › Which customers take longest to pay?
• › Pause chasing on invoice INV-3381 while the dispute is open.
• › Add a note to Northwind's record that their finance contact is away until Monday.

Questions

Is this an official Chaser MCP server?

No. It is Memtro's MCP server with Memtro's Chaser connector behind it: the connector reads Chaser through its API with the credentials you connect on Dashboard → Connections, and Chaser 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 Chaser?

Only when you ask, and only what it has been granted: add an internal note to a Chaser customer, edit it or delete it; create a credit-control task, or complete, cancel, reschedule or reassign one; pause chasing of an invoice, a customer or the whole organisation, or resume it (resuming emails customers reminders again); add a customer, or change its name, main contact or status (archive or reactivate); add, change, archive or remove a contact person who receives a customer's reminders; put up to 50 customers on a chasing schedule. 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