Paidnice MCP¶
The receivables layer of the finance stack: Xero or QuickBooks holds the ledger, Paidnice holds what happens after the invoice goes out, and over MCP an assistant reads both in one chat. It triages customer replies by what each account owes, checks whether a "we already paid" claim has actually landed, briefs you before a call and keeps contacts current. Hosted remote server with OAuth sign-in; one organization per connection.
Server type: Hosted (Streamable HTTP, JSON-RPC 2.0)
Endpoint: https://api.paidnice.com/mcp
Auth: OAuth 2.1 (sign in to Paidnice and choose the organization and access)
Server: com.paidnice/mcp v1.0.0 in the official MCP registry
Works with: Claude, ChatGPT, Claude Code and any client that accepts a remote MCP server
Ledger: Xero and QuickBooks Online (Paidnice shares each customer's ledger ID so replies match the right account)
Publisher: Paidnice (paidnice.com); Xero Global App Awards 2026 App of the Year; Pro and Custom plans include the server
Listing: mcpservers.org /all, October 15, 2026 midday sweep
Why This Matters for Operators¶
A ledger connector tells you what is on the books. It does not tell you who replied this morning, which of those replies is a dispute, or what each customer owes when you pick up the phone. That work lives outside the ledger, in inboxes and spreadsheets, and it is where cash gets stuck.
Paidnice is built for exactly that gap. The MCP server reads what Paidnice holds alongside a Xero or QuickBooks connector, so one prompt can check payments in the ledger, read replies in Paidnice, draft an answer and post the list to Slack. Replies carry the balance from the ledger, customer records pick up new names from cc lines and out-of-office messages, and a scheduled task can post a morning digest to the team channel. For accountants and bookkeepers the beta path answers across every client organization from one connection.
What You Can Do Today¶
| Capability | What it does |
|---|---|
| Read replies, contacts and invoices | Pull customer replies, contact records and invoice context for the connected organization |
| Triage replies by balance | Sort new emails and texts into promises, questions and disputes, ranked by what each customer owes in Xero or QuickBooks |
| Check "we already paid" | Look for the payment in the ledger, on the invoice or as a deposit waiting to be reconciled |
| Brief before a call | Last reply, who to speak to, whether you can text them, and the balance from the ledger |
| Keep contacts current | Pick up new names from cc lines and out-of-office replies, update the contact people and sync the change back |
| Client update in a minute | Draft a note on what a client's customers said this week and who needs a call |
A beta set is testing alongside these: every client in one chat for accountants, a month-end pack (DSO, overdue and collected per client), a cash forecast for the week, whole-ledger balance questions, a drafted-reminder approval queue, sending reminders and statements with approval, logging calls as they finish, logging promises and disputes so reminders wait, drafting policies by describing them, payment plans on the invoice, and working escalations with their context.
Business Relevance¶
- Finance teams get receivables follow-up in the same assistant that already holds the surrounding context, with each reply matched to the right ledger account
- Accountants and bookkeepers are the named audience: many clients, one connection, and the beta month-end pack answers DSO, overdue and collected per client
- Cash, not just records: the beta cash view targets what should land this week and what is at risk, which is the question a ledger report does not answer directly
- Approval-gated sending: beta send tools draft reminders and statements and wait for approval before they go
- No API key to copy: connect in about two minutes by pasting the server address and signing in
Integration with CorpusIQ¶
Receivables work needs three inputs: the ledger, the customer conversation and the payment status. CorpusIQ connects the ledger side - Xero, QuickBooks, Gmail, Outlook, Slack and the rest - over read-only tools, and Paidnice holds the post-invoice conversation layer. Connecting both to the same assistant lets it answer with the balance from the ledger and the reply from Paidnice in one pass. A REST API is also available if you need it outside MCP; the MCP server itself is scoped to the organization you choose at sign-in.
Limitations¶
- Xero and QuickBooks Online only: Paidnice runs on those two ledgers; other accounting systems are not covered
- One organization per connection: multi-client work across organizations is the beta path, not the current default
- Beta features are labelled as such: the live set is read replies, contacts and invoices with contact updates; the month-end pack, reminders, statements, payment plans and escalations are in beta
- Plan-gated: the MCP server is included with the Pro and Custom plans, not the free tier
- Read-first: core tools read replies, contacts and invoices; sending tools in beta are approval-gated
FAQ¶
Does the MCP server need an API key?¶
No key to copy. Add https://api.paidnice.com/mcp as a custom connector, sign in to Paidnice and choose the organization and what the assistant may do.
Which ledgers does it work with?¶
Xero and QuickBooks Online. Paidnice shares each customer's ledger ID so a reply matches the right account, and it works alongside a Xero or QuickBooks connector in the same chat.
Is it read-only?¶
The live core tools read replies, contacts and invoices and keep contacts current. The sending tools (reminders and statements) are in beta and draft for approval before anything goes out.
What does it cost?¶
The MCP server is included with the Pro and Custom plans; the free tier does not include it. A public REST API using bearer tokens is also documented.
Who is it for?¶
AI-first finance teams and the accountants and bookkeepers who manage many clients. The beta set is where the multi-client and month-end workflows live.