Rillet MCP server and Claude connector: what it reads and writes, what access it gets, how to connect

Rillet hosts an official remote MCP server at api.rillet.com/mcp, listed as a Claude connector, with 81 tools that read and write ERP records. Verified 21 Oct 2026.

Official remote MCP server · read & write
Claude connector · read & write

Hosting: Remote HTTP, hosted by Rillet (https://api.rillet.com/mcp). No local or open-source server.
Auth: OAuth2 sign-in, choosing one Rillet organisation, or a Rillet API key sent as an Authorization: Bearer header
Read / write: Read and write: the Claude directory lists 81 tools; by our count from the tool names, 38 read and 43 create, update or delete records
Works with: Claude.ai and Claude Desktop (connector), Claude Code and Cursor (per Rillet), other remote-capable MCP clients
Plan requirement: A valid Rillet account, per Rillet. Rillet doesn't document a plan tier or extra fee for MCP
Last changed: April 2026 (Rillet connector added to the Claude directory; MCP docs updated 24 Apr 2026)
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Rillet through MCP?

It reads your ledger, reports, and customer, vendor and contract records. It can also create, change and delete invoices, bills, contracts, customers, vendors and payment records.

Rillet says the server's tools mirror its Public API and that an agent only gets the tools the connected Rillet user can access.

Tools

The Claude directory lists 81 tools. By our count from the tool names:

Type	Count
Read: list, retrieve and get, plus six financial reports and a contract amendment preview	38
Write	43

How writes behave

Rillet doesn't document a draft step for MCP writes, so treat each create, update or delete as taking effect when the tool runs.
Rillet's API reference shows bills can carry a pending approval request where an approval workflow applies.

Money

Payment tools (create_a_bill_payment, create_an_invoice_payment) record a payment against a ledger account. The reference doesn't say they send funds.
setup_auto_payment returns a link a customer visits to set up automatic payment.

Good to know

The directory's description mentions creating journal entries by prompt. Its tool list includes only list_all_journal_entries.

Can

Read the chart of accounts, subsidiaries, invoices, bills, contracts, charges, reimbursements, journal entries, bill and invoice payments, and custom fields
Read the payment method a customer has set up for auto-payment (get_payment_method), a sensitive read
Run the income statement, balance sheet, cash flow, trial balance, executive P&L and ARR waterfall reports
Create, update and delete customers, vendors, products, invoices, bills, credit memos and vendor credits, and apply vendor credits (write, takes effect directly)
Update invoice and credit memo taxes, mark an invoice's sent status, and delete charges and reimbursements (write)
Create, amend, end and delete contracts, and upsert or delete usage records (write)
Record bill and invoice payments, delete bill payments, and start customer auto-payment setup (write, affects cash and receivables records)

Cannot

Create or edit journal entries through the Claude connector (no such tool in the directory's 81-tool list, though Rillet's API has the endpoint)
Use more than one organisation per sign-in (you pick one organisation when you authorise, per Rillet)
Reach tools the connected Rillet user can't access (per Rillet)

What access does it get?

The same access as the Rillet user who signs in, for one organisation; Rillet doesn't document a read-only mode for MCP.

Where	Scopes and permissions (as documented)	Admin requirement
Claude connector and OAuth2 sign-in (remote)	Rillet's docs don't list the scopes requested. The server's published OAuth metadata advertises two scopes, read and write. Rillet doesn't document what each scope grants, or whether a client can request only read to get a read-only connection. Sign-in shows an organisation picker and an Allow access button.	Rillet doesn't document who can authorise. Claude Team/Enterprise: an Owner adds the connector before members can connect.
API key as a Bearer token (remote, other clients)	No scopes documented; the key reaches the Rillet Public API. Rillet says you ask your Rillet team to enable API access, then create keys in Organization Settings. Rillet doesn't document whether a key is limited by its creator's role or by the read and write scopes, so treat a key as organisation-wide access and prefer OAuth for MCP.	Not documented by Rillet beyond the Organization Settings API access page.

How do I connect it?

Add the Rillet connector from Claude's directory, or point Claude Code or Cursor at https://api.rillet.com/mcp and sign in to your organisation.

In Claude, open Settings › Connectors and click Browse connectors (Rillet's documented steps), or open https://claude.com/marketplace/connectors/rillet.
Search for Rillet and click +.
In the Rillet browser window, pick your organisation and click Allow access.
Start a new chat and ask, for example, which customers you have in Rillet.
Team/Enterprise: an Owner must add the connector before members can connect.

Write-capable. Review each write tool call before approving it.

What should a finance team watch for?

Write access is the main risk. Of the 81 tools, 43 change records by our count, and Rillet documents no read-only setting, so the role of the user who signs in is your main control.

Least privilege: Rillet says tools follow the connected user's access, so connect through OAuth with a Rillet user whose role covers only what the agent needs. Rillet doesn't document how to restrict the server to read tools, or whether an API key follows a user's role.
Writes take effect when the tool runs; Rillet documents no MCP draft step. Delete tools cover bills, invoices, contracts, customers, vendors, products, charges, reimbursements, credit memos, vendor credits, usage records, custom field values and bill payments.
Tools that touch money records: create_a_bill_payment, create_an_invoice_payment, delete_a_bill_payment, apply_vendor_credit and setup_auto_payment. Approve each call yourself.
A customer create or update can turn on Rillet's send_invoices_automatically setting. Rillet's API reference says invoices for that customer are then emailed automatically on the invoice date, so one write can reach people outside your company.
Rillet's Public API allows 600 requests per minute per API key in production, with 429 errors over the limit. It doesn't state a separate MCP limit.
If you use an API key in a client config such as Cursor's mcp.json, it sits in plain text. Keep that file out of version control and synced folders, and prefer OAuth sign-in. Rillet's documented Cursor config runs npx -y mcp-remote, a third-party npm bridge, with no version pinned; admins may want to pin one.
Rillet's privacy policy (effective 20 Nov 2024) doesn't address AI model training for customer data beyond Google API data. Check Rillet's and your AI provider's terms.
Customer, vendor and invoice text comes back as free text. An injected instruction in a memo or description could push the agent to create, delete or record a payment, so keep human approval on.

How could finance teams and accounting firms use it?

Use the read tools for questions and reporting, and the write tools only for drafting changes a person reviews and approves call by call.

Inside a company

Ask for the income statement or executive P&L for the quarter and a short variance commentary, without exporting reports.
List overdue invoices and draft follow-up notes for a person to send.
Pull the ARR waterfall and contract list to explain revenue movements at month end.
Prepare new vendor or customer records from a request, with a person approving each create call.

At an accounting firm

Summarise a client's trial balance and balance sheet before a review meeting.
Check invoices and recorded payments against the client's bank evidence before sign-off.
Review contracts and usage records for a revenue recognition question the client raised.
Plan for one connection per client organisation, since each sign-in selects one organisation.

Whatever the use, keep a person approving every call that changes Rillet, and treat AI-produced figures as drafts until they tie to Rillet's reports.

Want Rillet connected to Claude for your team?

We set up scoped connections and a review step before anything changes your books, for a fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-21	Directory lists 81 tools (38 read and 43 write by our count); server's OAuth metadata advertises read and write scopes	claude.com/marketplace/connectors/rillet
2026-04-24	Rillet MCP setup guide updated with Claude directory steps	docs.api.rillet.com/v2.0/docs/mcp
2026-04	Rillet connector added to the Claude directory	claude.com/marketplace/connectors/rillet

FAQ

Is this official?

Yes. Rillet documents and hosts the server at api.rillet.com and publishes the Claude connector, which the Claude directory marks as Anthropic verified.

Is it free?

Rillet says you need a valid Rillet account and doesn't state a separate MCP price. You also need a Claude or other AI client plan.

Does it change data in Rillet?

Yes. By our count from the directory's tool names, 43 of the 81 tools create, update or delete records, including invoices, bills, contracts and payment records. Rillet documents no draft step, so approve each write call.

Is my data used to train models?

Rillet doesn't address this for MCP, and its privacy policy only covers Google API data on this point. Check Rillet's terms and your AI provider's terms.

Can my accountant use it on my behalf?

Rillet doesn't document this. Access follows the Rillet user who signs in, so the connection carries that login's permissions for one organisation.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.