Rootline MCP connector

Connecting Rootline to Claude takes two steps. First, open Elaichi, choose Rootline, and paste in your Rootline API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on Rootline payments are available in your conversations.

Yes. Once Rootline is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Rootline once and every client you use picks it up.

With Rootline connected, an agent can create a new payment, look up an existing payment by its ID to see its amount and status, cancel a payment that has not been captured, capture an authorized payment, and issue a refund. In practice that means a support agent can ask Claude to find a customer's Rootline payment and refund it, or an operations lead can ask it to capture a payment once an order ships. This connector covers those five actions on Rootline payments and nothing beyond them.

An agent working through Elaichi can only do what the Rootline API key it was connected with allows, and Elaichi can narrow that access further but never widen it. If the key can only read payments, the agent can only read payments. Restrictions in Elaichi let you take actions such as refunds or cancellations away from the AI entirely, so Rootline access through Elaichi is always equal to or smaller than what the person who connected it holds.

Yes. One person connects Rootline in Elaichi with the API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so when someone refunds or cancels a Rootline payment the audit log records their name, not a shared account.

Yes. Restrictions in Elaichi apply per action, so you can allow an agent to look up Rootline payments while blocking refunds, cancellations, or captures. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

When you offboard a person in Elaichi, their access to Rootline through every client ends at once. If they were using a shared Rootline connection, it keeps working for everyone else on the team. If you want to remove Rootline entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other connected client.

Yes. Rootline is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Rootline. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Rootline call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Rootline: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.