Rillet

Query a live general ledger and post to it.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Rillet connector does

The Rillet MCP server connects Rillet's AI-native ERP to Claude, ChatGPT or any MCP-compatible agent, so a general ledger can be queried in plain English. It is not read-only. Of the 81 tool names Anthropic's directory publishes, 43 write — creating invoices and bills, recording payments, and deleting records across every subledger Rillet keeps.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Rillet tools (81)

  • amend_a_contract
  • apply_vendor_credit
  • create_a_bill
  • create_a_bill_payment
  • create_a_contract
  • create_a_credit_memo
  • create_a_customer
  • create_a_product
  • create_a_vendor
  • create_a_vendor_credit
  • create_an_invoice
  • create_an_invoice_payment
  • create_field
  • create_field_value
  • delete_a_bill
  • delete_a_bill_payment
  • delete_a_charge
  • delete_a_contract
  • delete_a_credit_memo
  • delete_a_customer
  • delete_a_product
  • delete_a_reimbursement
  • delete_a_usage_record
  • delete_a_vendor
  • delete_a_vendor_credit
  • delete_an_invoice
  • delete_field_value
  • end_an_open_ended_contract
  • get_api_key_information
  • get_fields
  • get_payment_method
  • list_all_accounts
  • list_all_bills
  • list_all_charges
  • list_all_contract_item_usage_records
  • list_all_contracts
  • list_all_credit_memos
  • list_all_customers
  • list_all_invoice_payments
  • list_all_invoices
  • list_all_invoices_payments
  • list_all_journal_entries
  • list_all_products
  • list_all_reimbursements
  • list_all_subsidiaries
  • list_all_vendor_credits
  • list_all_vendors
  • list_bill_payments
  • preview_contract_amendment
  • retrieve_a_bill
  • retrieve_a_charge
  • retrieve_a_contract
  • retrieve_a_credit_memo
  • retrieve_a_customer
  • retrieve_a_product
  • retrieve_a_reimbursement
  • retrieve_a_subsidiary
  • retrieve_a_vendor
  • retrieve_a_vendor_credit
  • retrieve_an_organization
  • retrieve_balance_sheet_report
  • retrieve_cash_flow_statement_report
  • retrieve_executive_pl_report
  • retrieve_income_statement_report
  • retrieve_trial_balance_report
  • retrieve_waterfall_report
  • setup_auto_payment
  • update_a_bill
  • update_a_contract
  • update_a_credit_memo
  • update_a_customer
  • update_a_product
  • update_a_vendor
  • update_a_vendor_credit
  • update_an_invoice
  • update_field
  • update_field_value
  • update_invoice_sent_status
  • update_taxes_for_a_credit_memo
  • update_taxes_for_an_invoice
  • upsert_a_usage_record

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Full-replace update semantics are the sharpest hazard here. Rillet flags this as IMPORTANT on its invoice, bill, credit memo, vendor credit, customer and product update endpoints: the operations are PUT, all fields must be present, and an omitted field is set to null, wiping existing data. Rillet's stated remedy is to retrieve the whole record first and resend it.
  • No safety annotations could be read. The endpoint returns HTTP 401 to an anonymous client, so the MCP readOnlyHint and destructiveHint values — the fields a client uses to prompt for confirmation — are unverified for every one of the 81 tools. The read/write split published above is inferred from verb prefixes and Rillet's own endpoint documentation, not from annotations.
  • The two OAuth scopes are coarse. write covers creating invoices, recording payments and deleting records with one grant; read covers every report and subledger with the other. There is no per-domain or per-destructiveness split of the kind some connectors publish.
  • Deletion preconditions are advisory only. Rillet documents what to verify before each delete, but those are instructions to a reader, not constraints the API enforces on a caller.
  • 60 requests per rolling minute, then HTTP 429 — shared across every integration using the same credentials.
  • Pagination is cursor-based and capped. Lists default to 25 records and allow at most 100 per page, and Rillet states cursors expire after two hours. Long ledger walks interact directly with the rate limit.
  • API versioning changes underneath you. Rillet documents X-Rillet-API-Version as the way to pin behaviour and warns that the no-header default moved from version 1 to the latest version on 1 August 2026. It is not documented whether the MCP server pins a version on your behalf.
  • Idempotency is opt-in. Rillet supports an Idempotency-Key header on POST requests and stores the response for 24 hours, but nothing states that the MCP server sets one — so a retried create is not automatically safe from duplicating a record.
  • Multi-book restrictions apply. Rillet documents that only primary and adjustment-overlay book_id values work with report and journal-entry endpoints, and that multi-book support applies to v4 only.
  • The published tool list is a floor, not a ceiling, and 22 documented mutating operations sit outside it. Scope any deployment to what the OAuth grant and the Rillet user's own permissions allow, not to the 81 names.

Frequently asked questions

Can the Rillet MCP server change my accounting records, or only read them?

It changes them. Anthropic's directory publishes the permission label Read and write, and 43 of the 81 listed tool names are mutating verbs — 12 create, 13 update, 13 delete, plus five one-off actions. Only 38 read. Every financial subledger Rillet exposes has a delete tool attached to it, so this is not a reporting connector with a few writes bolted on.

Does Rillet MCP let an agent post journal entries to the general ledger?

The directory listing does not include one, but Rillet's own API does. Anthropic's snapshot names only list_all_journal_entries, a read. Rillet's published v4 OpenAPI specification documents POST, PUT and DELETE on /journal-entries, and Rillet's connector description advertises creating journal entries by prompt. Treat GL posting as reachable and gate it deliberately.

How many tools does the Rillet MCP server actually expose?

Anthropic's directory lists 81 tool names, but that is a floor rather than a total. Rillet documents the MCP server as implementing the same features as its Public API, whose v4 specification defines 117 operations. Rillet also states an agent only sees tools the signed-in Rillet user can reach, so the real surface varies per user.

Can you connect Rillet MCP with read-only access?

Yes, in principle. Rillet's RFC 9728 resource descriptor advertises exactly two scopes, read and write, so a token can carry read without write. Whether your MCP client lets you decline the write scope at the consent screen is a client question, not a Rillet one. The scopes are coarse: read covers every report and subledger at once.

What happens if I update a Rillet record through an agent?

You may silently erase fields you never mentioned. Rillet marks its update endpoints as full-replace PUT semantics and warns that omitting any field sets it to null, wiping existing data. Its documented remedy is to retrieve the record first and resend every existing field alongside the change. An agent that patches conversationally will not do that by default.

Does Rillet MCP need a paid plan or an admin to switch on?

You need a Rillet account, and API access is not self-serve. Rillet's setup page lists a valid Rillet account as the only stated prerequisite for MCP. Its getting-started guide adds that you contact your Rillet team to enable API access before keys can be created. Authorisation is per organisation — you pick one during the OAuth redirect.

Is there a rate limit on the Rillet MCP server?

Yes. Rillet documents a maximum of 60 API requests over a rolling one-minute window, with requests above that threshold failing with HTTP 429. That budget is shared with any other integration using the same credentials. Agents that fan out across subsidiaries or paginate long ledgers can exhaust it quickly, since list responses default to 25 records per page.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Rillet to work.

Connect Rillet once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio