Ramp

Ramp

Interact with Ramp's Developer API to run analysis on your spend and gain insights leveraging LLMs

27
Stars
16
Forks
0
Releases

Overview

ramp-mcp is a Model Context Protocol server for retrieving and analyzing Ramp data or running tasks via the Ramp Developer API. To handle token and input size limitations, the server implements a simple ETL pipeline and an ephemeral SQLite database kept in memory for analysis by an LLM. By default, all requests target the demo environment; you can switch to production by setting RAMP_ENV=prd. The server exposes a suite of tools categorized as database tools (process_data, execute_query, clear_table), fetch tools (get_ramp_categories, get_currencies), and load tools that load various Ramp data into the ephemeral store. Each load tool maps to a specific Ramp scope (e.g., transactions:read, reimbursements:read, bills:read, locations:read, departments:read, bank_accounts:read, vendors:read, entities:read, limits:read, spend_programs:read, users:read) and enables data ingestion for subsequent queries and analysis. The README also notes performance considerations for large datasets and provides usage instructions for running via uv with Ramp client credentials, configuring environment variables, and optionally integrating with Claude Desktop. It emphasizes enabling the appropriate scopes on the Ramp client and including them when starting the server.

Details

Owner
ramp-public
Language
Python
License
MIT License
Updated
2025-12-07

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.”

Audience

DevelopersSet up and operate the MCP server to analyze Ramp spend data via the Developer API.
Data scientistsExperiment with LLM-driven analysis using the in-memory ETL data store.
LLM integratorsIntegrate Ramp data analysis with Claude or other LLMs using the MCP server.

Tags

RampMCP serverETLin-memory SQLiteLLM analysisDeveloper APIdata retrievaldata loadingscopesClaude Desktop