Ramp builds an MCP server enabling natural-language analysis of business spend data with Claude
Ramp's business data was accessible only through API calls, with no way to query or understand spend using natural language without writing code.
The initial MCP prototype ran into scaling issues—miscalculations, limited context windows, input size limits, and high token usage—and could not reliably handle more than a few hundred transactions.
After switching to a SQL-based paradigm with an in-memory SQLite database, Claude could accurately analyze tens of thousands of spend events, and the solution even worked with the free version of Claude due to reduced token usage.
Frequently asked questions
What did this team achieve with this AI workflow?
After switching to a SQL-based paradigm with an in-memory SQLite database, Claude could accurately analyze tens of thousands of spend events, and the solution even worked with the free version of Claude due to reduced…
What tools did this team use?
Ramp MCP, FastMCP, Claude Desktop, Claude, SQLite, Ramp developer API, Model Context Protocol, OLAP.
What results were reported?
Data analysis scale improvement: from struggling with a few hundred data points to accurately analyzing tens of thousands of spend events; Initial results quality: mind-blowing (source-reported, not independently verified).
What failed first in this deployment?
The initial MCP prototype ran into scaling issues—miscalculations, limited context windows, input size limits, and high token usage—and could not reliably handle more than a few hundred transactions.
How is this finance ops AI workflow structured?
Natural language query trigger → Pull data from Ramp API → ETL into in-memory SQLite → Claude executes SQL queries → Generate analysis and visualizations.