Overview
Features
Ephemeral in-memory SQLite database
Uses an in-memory SQLite database to store transformed Ramp data for analysis by an LLM without persisting data.
ETL pipeline for LM-friendly analysis
Implements a simple ETL flow to extract, transform, and load Ramp data into the ephemeral store for efficient LM processing.
Database tools
Provides tools to set up, process data, query, and clear the ephemeral database (process_data, execute_query, clear_table).
Fetch tools
Includes tools to fetch metadata directly from Ramp (get_ramp_categories, get_currencies).
Load tools with scope mappings
Data ingestion commands mapped to specific Ramp scopes (e.g., transactions:read, reimbursements:read, etc.).
Demo by default; production via RAMP_ENV
Requests default to the demo environment and can be switched to production by setting RAMP_ENV=prd.
CLI-based server start with uv
Run the MCP server via uv with Ramp client credentials and a selected set of scopes.
Claude Desktop configuration guidance
Includes a Claude Desktop configuration example for integrating ramp-mcp with Claude.”
Who Is This For?
- Developers:Set up and operate the MCP server to analyze Ramp spend data via the Developer API.
- Data scientists:Experiment with LLM-driven analysis using the in-memory ETL data store.
- LLM integrators:Integrate Ramp data analysis with Claude or other LLMs using the MCP server.




