Ramp MCP Server
Connect AI agents to your Ramp corporate cards and expense data over the Model Context Protocol.
Updated
What is Ramp MCP?
The Ramp MCP server is a Model Context Protocol server that connects AI agents and assistants to your Ramp account, giving them structured, permissioned access to corporate card and expense-management data such as transactions, reimbursements, bills, vendors, and spend limits.
Ramp hosts an official remote server at https://mcp.ramp.com/mcp (with a sample-data variant at https://demo-mcp.ramp.com/mcp). It uses OAuth: when a client connects, you sign in to Ramp in the browser and approve access, so no long-lived API keys are stored in the client config. Ramp also publishes an open-source, self-hosted implementation (ramp-public/ramp_mcp) that you run locally against the Ramp Developer API using your own client credentials and scopes.
In practice an agent uses the server to pull and analyze spend data in natural language — building curated views of company spending, finding potential cost savings, and navigating the business hierarchy — rather than you clicking through dashboards or writing API calls by hand.
Tools the Ramp MCP server exposes
| Tool | What it does |
|---|---|
| load_transactions | Load card transaction data into the working set for analysis. |
| load_reimbursements | Load employee reimbursement records. |
| load_bills | Load bills / accounts-payable data. |
| load_vendors | Load vendor records. |
| load_departments | Load department records for the business hierarchy. |
| load_users | Load user / employee records. |
| load_spend_limits | Load spend limit configurations. |
| load_spend_programs | Load spend program definitions. |
| get_ramp_categories | Fetch the list of Ramp spend categories. |
| execute_query | Run a SQL query against the loaded data for analysis. |
Connect the Ramp MCP server
Claude (remote, OAuth)
- 1
Add the Ramp connector
In Claude, go to Settings > Connectors > Add custom connector and enter the server URL https://mcp.ramp.com/mcp (use https://demo-mcp.ramp.com/mcp for sample data).
- 2
Authenticate with Ramp
When prompted, sign in to your Ramp account in the browser and approve the requested access (OAuth). No API keys are stored in the client.
- 3
Verify the connection
Confirm the Ramp connector shows as connected, then ask the agent to load and summarize recent transactions.
Uses Ramp's official hosted server; you authenticate in the browser.
Cursor (self-hosted, open source)
- 1
Create Ramp API credentials
In the Ramp developer settings, create a client ID/secret and enable the read scopes you need (e.g. transactions:read, bills:read).
- 2
Add the server to Cursor
Edit ~/.cursor/mcp.json to launch the server, passing RAMP_CLIENT_ID, RAMP_CLIENT_SECRET, RAMP_ENV (demo or prd) and the enabled scopes (-s) to the ramp-mcp command.
- 3
Restart and test
Restart Cursor, confirm the Ramp tools appear, and prompt the agent to load transactions and run a spend query.
Runs Ramp's open-source ramp-public/ramp_mcp locally with your Developer API client credentials.
Sample use cases
A finance team wants a weekly spend summary without logging into the dashboard.
A scheduled agent loads recent transactions and posts a categorized spend summary with flagged outliers.
An operator asks ad-hoc questions about company spend in natural language.
The agent queries transactions and departments to answer questions like top vendors or spend by team.
A team reviews accounts payable before a close.
The agent loads bills and vendors and surfaces upcoming or unusual items for review.
Security & permissions
The remote server at https://mcp.ramp.com/mcp authenticates with OAuth: you sign in to Ramp and approve access, so the agent acts within your Ramp permissions and no static API key lives in the client config. Access can be revoked from Ramp at any time.
The self-hosted server uses Ramp Developer API client credentials (client ID/secret) plus explicit scopes you enable per tool (e.g. transactions:read, bills:read), so the agent only touches the data classes you grant. Both paths expose sensitive financial data (card transactions, reimbursements, bills, vendors), so scope grants to least privilege and restrict who can connect.
Using Ramp MCP with Gamut
In a Gamut workflow, the Ramp MCP server becomes a tool an agent can call on a schedule or in response to an event — Gamut manages the authenticated connection so the agent can pull transactions, reimbursements, or bills and reason over them. For example, a scheduled agent can summarize the week's card spend, flag transactions over a threshold, or surface potential savings, then hand the result to another step (a Slack message, a report, or a review queue). The agent only reads what its granted Ramp scopes allow.
Frequently asked questions
What is the Ramp MCP server?
It is a Model Context Protocol server that gives AI agents structured, permissioned access to your Ramp account so they can fetch and analyze transactions, reimbursements, bills, vendors, and spend data. Ramp hosts an official remote server at https://mcp.ramp.com/mcp and also publishes an open-source self-hosted version.
Is the Ramp MCP server free?
There is no separate charge for MCP. The hosted remote server is available to existing Ramp customers as part of their account, and the open-source self-hosted server is free to run — you just supply your own Ramp Developer API credentials.
How do I connect the Ramp MCP server to Claude?
Add a custom connector in Claude's settings pointing to https://mcp.ramp.com/mcp, then sign in to Ramp in the browser when prompted (OAuth) and approve access. Use https://demo-mcp.ramp.com/mcp to try it with sample data.
Is it hosted by Ramp or self-hosted?
Both. Ramp operates an official hosted remote server (OAuth sign-in, no API keys in your config), and you can alternatively self-host the open-source ramp-public/ramp_mcp server locally using your Ramp Developer API client credentials and scopes.