Rev.io MCP server for AI agents.

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 335 Rev.io actions across customers, inventory items, requests and payments, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Rev.io.

Rev.io login name of the API user (create a dedicated API-only user in Rev.io and give its role only the permissions…, Rev.io client code (the instance code, e.g, Password of the Rev.io API user and Optional. Plus your host. The free call account { op: "connections.requirements", service: "rev_io" } lists exactly what to paste.

Only if its key allows it, and only with an explicit confirmation. 38 Rev.io actions are destructive, including delete contact, reverse bill and delete product. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

actionlake paces every call to the limits in the Rev.io service file: 300 calls a minute per connection. Repeated reads are answered from cache (160 Rev.io actions can be), which never reaches Rev.io.

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (335 Rev.io actions page). Cache hits, searches, dry runs and calls Rev.io refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

The Rev.io REST API v1 (OpenAPI 3.0, developers.rev.io API Explorer) at restapi.rev.io by default, or the base URL set when you connect. It is built from Rev.io's documentation as read on 23 October 2026. 335 actions in 73 areas, each one in the signed service file (version 1.0.0).

Yes. ask joins Rev.io to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. Rev.io maps crm.company, which 227 other connectors also map.

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Rev.io credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.