Can AI agents automate Ramp?

Ramp is automatable today through the Developer API. This record is Ramp corporate cards, expenses, reimbursements, bills, travel, and accounting workflows, including the vendor-hosted MCP at https://mcp.ramp.com/mcp. It is not Brex, Pleo, or SAP Concur. Production API calls go to https://api.ramp.com/developer/v1; sandbox is https://demo-api.ramp.com. OAuth 2.0 client-credentials is the documented server-to-server path: admins create an app under Company → Developer, then POST /developer/v1/token with HTTP Basic client_id:client_secret. Those access tokens last about 10 days and do not refresh. Third-party and multi-tenant apps must use authorization-code against https://app.ramp.com/v1/authorize (sandbox https://demo.ramp.com/v1/authorize). GET /developer/v1/transactions is the opened first-call example. Webhooks subscribe at POST /developer/v1/webhooks and verify X-Ramp-Signature HMAC-SHA256. Events cover transactions, bills, reimbursements, purchase orders, users, and related resources. First-party MCP is hosted at https://mcp.ramp.com/mcp, with demo data at https://demo-mcp.ramp.com/mcp. Off-the-shelf clients use OAuth; custom clients need a redirect-URI allowlist. Tool groups cover spend analysis, approvals, expense submission, card lock/unlock, policy Q&A, Agent Cards, and trips. Bill approvals are not yet available via MCP. Admins control MCP access from Company → Integrations → Ramp MCP. The official CLI (github.com/ramp-public/ramp-cli) uses ramp auth login (browser OAuth) or client-credentials agent login, with --agent JSON output for bills, cards, transactions, reimbursements, and travel. iPaaS catalogs were not opened. Computer-use viability is unassessed. API and CLI each score 8. API is the best path because it is the durable OAuth control plane and does not depend on a CLI login session or evolving MCP tool names.

Best path today: api · Overall automatability: 8/10