Skip to content

Ramp MCP connector

Connect Ramp to Claude, ChatGPT, Cursor and any MCP client through Elaichi, so your finance team can review and update Ramp's chart of accounts, accounting connections and field options in plain language, with every change logged.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Ramp to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Ramp once

  1. Open Connections, choose Add connection, and pick Ramp.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Ramp app, then approve. Ramp needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

ramp
Ramp
Bill
Brex
Cledara
Procurify
Zip
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Ramp MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Ramp MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Ramp MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Ramp to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Ramp through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Accounting

    Keep the chart of accounts current

    When a new general ledger account is opened in the ERP, add the matching accounting account in Ramp and fix the name or code on an existing one without opening the settings screen.

  • Finance

    Tidy up departments, locations and classes

    List every accounting field option in Ramp, spot duplicates and stale entries, and rename or retire them so cardholders stop picking the wrong one.

  • Controllers

    Limit which options cardholders can choose

    Set filter rules on Ramp accounting fields so a team only sees the departments or cost centers that apply to it, and clear out old rules in bulk when the structure changes.

  • Finance systems

    Check on the accounting connection

    Ask which accounting connections Ramp has, whether one needs reactivating, and mark a connection ready to migrate when the company moves to a new ledger.

  • Accounting

    Code spend to the right account

    Create an accounting coding in Ramp that ties spend to the correct account, department and class ahead of the close, instead of fixing it after the export.

  • Operations

    Stand up a new entity's accounting setup

    Create the accounting entity in Ramp for a newly acquired company, then add its accounts and field options so its spend is coded properly from the first month.

Try asking

  • “Summarize last week's Ramp transactions by accounting account.”
  • “Which Ramp cards spent most this month?”
  • “List Ramp accounting connections added since April.”

See all 246 Ramp tools below

Compare

Elaichi vs Zapier MCP vs Composio for Ramp

All three can connect Ramp to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Ramp, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Ramp tools Allow or restrict single Ramp tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Ramp call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Ramp tools for your AI agents

246 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ramp, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 242 of 246 Ramp tools here. Connect Ramp and call search_tools or tools/list over the MCP endpoint for the complete set.

See it in Elaichi

What connecting Ramp gets you

6 screens from the product, each doing one job for your Ramp account.

The agent

Ask about Ramp spend, get real answers.

Plain language questions run against live Ramp transactions, cards and accounting accounts.

  • transactions
  • cards
  • accounting accounts
  • reimbursements

Ask Elaichi to work across your apps.

Summarize last week's Ramp transactions by accounting account.

Which Ramp cards spent most this month?

List Ramp accounting connections added since April.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Ramp here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

246 Ramp tools ready without custom code.

Browse Ramp resources and methods for accounts, connections, codings and reimbursements.

  • List all Ramp accounting accounts
  • Create a Ramp accounting account
  • Get single Ramp accounting account by ID
  • Update a Ramp accounting account by ID
ElaichiTools
Tool Action Description
List all Ramp accounting accounts List List general ledger accounts in Ramp with optional filters by remote_id, code, active status, and accounting connection. Returns: accounting_connection_id, classification, code, created_at, entity_remote_ids, gl_account_category_info, id, is_active, name, provider_name, ramp_id, updated_at, visibility, remote_id, is_synced. If the account belongs to an inactive accounting connection,…
Create a Ramp accounting account Create Upload general ledger accounts. Returns: accounting_connection_id, gl_accounts, uploaded. Required: gl_accounts.
Get single Ramp accounting account by ID Get Get a single Ramp general ledger account by id. Returns: accounting_connection_id, classification, code, created_at, entity_remote_ids, gl_account_category_info, id, is_active, name, provider_name, ramp_id, updated_at, visibility, remote_id, is_synced. If the account belongs to an inactive accounting connection, supply accounting_connection_id to retrieve it. Required: id.
Update a Ramp accounting account by ID Update Update the name or code of a general ledger account in Ramp. Returns: accounting_connection_id, classification, code, created_at, entity_remote_ids, gl_account_category_info, id, is_active, name, provider_name, ramp_id, updated_at, visibility, remote_id, is_synced. Required: id.
Delete a Ramp accounting account by ID Delete Delete a general ledger account in Ramp by id. Returns an empty 204 response on success. Required: id.

Toolboxes

Every team gets its own Ramp toolbox.

Finance, Accounting and Procurement each work from a toolbox scoped to them.

  • Finance
  • Accounting
  • Procurement
  • People Ops
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Ramp · transactions and budgets

Ramp starter 18 Mar 4, 2026

Accounting toolbox

Ramp · accounting accounts and codings

— 9 Mar 2, 2026

Procurement toolbox

Ramp · vendors and bills

— 24 Feb 27, 2026

People Ops toolbox

Ramp · reimbursements and card limits

Ramp starter 6 Feb 19, 2026

Engineering toolbox

Ramp · Ramp accounting connections

— 31 Jan 30, 2026

Leadership toolbox

Ramp · spend limits and approvals

— 12 Jan 22, 2026

Shared connections

Share a Ramp connection, never the credential.

See who connected each Ramp account and which teams and members use it.

  • Finance HQ
  • Accounting
  • Procurement
  • People Ops
ElaichiConnections
Connection Scope Status Access
RA

Ramp (Finance HQ)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RA

Ramp (Accounting)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RA

Ramp (Procurement)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RA

Ramp (People Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
RA

Ramp (Sales EMEA)

Connected by Ryan Hayes

Personal • Active Not shared
RA

Ramp (Marketing)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which Ramp record.

Every call is logged with time, actor, action, type and Ramp resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Ramp Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Ramp Transactions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Ramp Transactions List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and Ramp work finishes.

Ramp transactions are fetched, grouped, drafted into a digest, approved, then posted back.

Ramp digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch transactions

    Ramp

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Ramp

    Queued

Collections and dashboards

Ramp spend numbers arrive before you ask.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

Ramp health

Refreshed 4 minutes ago · every 15 minutes · from the transactions collection

Live

Transactions

1,284 ↓ 12%

Cards

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Transactions created

Last 14 days

By team

Share of activity

Finance HQ 34%

Accounting 27%

Procurement 21%

People Ops 18%

FAQ

Frequently asked questions

How do I connect Ramp to Claude?

Two steps. First connect Ramp in Elaichi: Ramp connects over OAuth, but it needs an OAuth application you register inside Ramp yourself, so somebody with admin rights brings a client ID and secret once, and after that everyone signs in with their own Ramp login. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Nobody else on the team handles a credential from that point on.

Does Ramp work with ChatGPT and Cursor as well as Claude?

Yes. Once Ramp 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 Ramp once and every client picks it up.

What can an AI agent actually do with my Ramp data?

With Ramp connected, you can ask for a list of your accounting accounts, add or rename one, review the department, location and class options cardholders pick from, set rules for which options each team sees, create accounting codings, and check on or reactivate your accounting connections. Ramp exposes a lot of actions, so short concrete asks work best, such as "list our Ramp accounting field options" rather than a long paragraph.

Does connecting Ramp give the AI everything in my Ramp account?

No. Every request to Ramp runs as the person who signed in, so the AI can only see and change what that person's own Ramp role already allows. Elaichi can narrow that further, for example to read-only on the chart of accounts, but it can never grant more than the person has in Ramp.

Can my team share one Ramp connection?

Yes. One person connects Ramp in Elaichi and shares it with a team, and nobody else ever sees the client ID, secret or any token. Each teammate still signs in as themselves, so the audit log records who changed which accounting account or field option in Ramp.

Can I stop an agent from deleting or changing things in Ramp?

Yes. Restrictions in Elaichi work per action, so you can allow listing Ramp accounting accounts while blocking deletes, updates or bulk removals of field options. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Ramp connection when someone leaves?

When you offboard someone in Elaichi, their access to Ramp through every AI client ends at once. If they had shared a Ramp connection with the team, it keeps working for everyone else. Disconnecting Ramp once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Ramp MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Ramp 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.

Is Elaichi an alternative to Zapier MCP for Ramp?

Yes. Both let Claude, ChatGPT or Cursor use Ramp. 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 Ramp call.

How is Elaichi different from Composio for Ramp?

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 Ramp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Ramp in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.