MCP overview

The Ramp MCP server lets AI assistants call Ramp tools from a conversation. It is the recommended surface for Claude, ChatGPT, Cursor, Perplexity, and other clients that support remote MCP.

Use MCP when you want the assistant to stay in context: inspect spend, answer policy questions, look up Ramp objects, or request Agent Card credentials without copying data between apps.

Server URLs

Use production when you are ready to authorize against your Ramp workspace. Use the demo server to explore with sample data and no Ramp account.

What is true today

Ramp documents MCP capabilities by outcome because the tool surface evolves. The exact list available to a given user also depends on Ramp permissions, admin MCP access controls, client support, and OAuth scopes.

• Read and analyze spend — search transactions; pull spend exports; query vendors, accounting categories, departments, entities; get treasury balances and the org chart.
• Understand policy and account context — ask policy questions, inspect fund restrictions, search help content, and explain why a transaction may have declined.
• Work with Ramp objects — retrieve cards, funds, users, vendors, departments, entities, reimbursements, bills, purchase orders, trips, and bookings where your role allows it.
• Make purchases — generate Agent Card credentials at purchase time when Agent Cards are enabled.
• Book travel where exposed — the current generated production tool list includes flight-booking submission alongside read-oriented trip and booking tools.

For exact names and parameters, use the MCP tools reference. It is generated from production and shows what the build-time token could see at generation time.

Permissions

Most company-wide data tools (spend exports, vendor management, GL coding) require admin or business-owner permissions. Employees see only their own data; admins see company-wide data. See Access & permissions for details.

What not to assume

• A tool listed in the public product capability map may not appear in your client until you reconnect and reauthorize.
• A tool listed in the reference may still fail if the authenticated user lacks the underlying Ramp permission or scope.
• Bill approvals are not currently available through Ramp MCP.
• File uploads, such as receipt images or PDFs passed through chat attachments, are not currently supported by Ramp MCP connections.

New tools ship continuously

The tool surface grows over time. Disconnect and reconnect your client (or run /mcp in Claude Code) to pick up new tools. For the full current list, see the MCP tools reference.

Ready to connect? See MCP setup.