Ramp MCP

Ramp MCP is the official Model Context Protocol server for Ramp, the corporate card and spend management platform. Rather than answering one question per API call, it runs a small extract and load step: the agent pulls a scoped slice of account data out of the Ramp developer API into an ephemeral in-memory database, then runs SQL against that copy. The design exists because finance questions are aggregations, and aggregating across a paginated API one page at a time is slow and lossy. The datasets it can load cover the operational core of a Ramp account: card transactions, reimbursements, bills and vendor records, spend limits and spend programs, and the users, departments, and locations that spend is attributed to. Reference data such as expense categories and currencies is available directly. Once loaded, the agent can group, filter, and join across those sets, so questions like spend by department over a period, vendors with recurring charges, or reimbursements outstanding by team are answered in a single pass. It is built for finance and operations teams that want ad hoc analysis without exporting to a spreadsheet, and for engineers building agents on top of company spend data. Access is governed by the scopes on the Ramp developer credentials used, and read-only scopes are the normal configuration, since the value here is analysis rather than moving money.