https://github.com/ramp-public/ramp-mcp
ramp-mcp
https://github.com/ramp-public/ramp-mcp
Last synced: 23 days ago
JSON representation
ramp-mcp
- Host: GitHub
- URL: https://github.com/ramp-public/ramp-mcp
- Owner: ramp-public
- License: mit
- Created: 2025-03-20T14:26:04.000Z (27 days ago)
- Default Branch: main
- Last Pushed: 2025-03-20T15:30:58.000Z (27 days ago)
- Last Synced: 2025-03-20T20:53:55.893Z (27 days ago)
- Language: Python
- Homepage:
- Size: 24.4 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
- Awesome-MCP-Servers-directory - Ramp - Interact with Ramp's Developer API to run analysis on your spend and gain insights leveraging LLMs (Finance)
- awesome-mcp-servers - Ramp - Retrieves and analyzes Ramp data via API, using an ETL pipeline and in-memory database for LLM processing (Table of Contents / Data Science Tools)
- awesome-mcp-servers - Ramp - Interact with [Ramp](https://ramp.com)'s Developer API to run analysis on your spend and gain insights leveraging LLMs (Official Servers)
README
# ramp-mcp: A Ramp MCP server
## Overview
A Model Context Protocol server for retrieving and analyzing data or running tasks for [Ramp](https://ramp.com) using [Developer API](https://docs.ramp.com/developer-api/v1/overview/introduction). In order to get around token and input size limitations, this server implements a simple ETL pipeline + ephemeral sqlite database in memory for analysis by an LLM. All requests are made to demo by default, but can be changed by setting `RAMP_ENV=prd`. Large datasets may not be processable due to API and/or your MCP client limitations.
### Tools
#### Database tools
Tools that can be used to setup, process, query, and delete an ephemeral database in memory.
1. `process_data`
2. `execute_query`
3. `clear_table`#### Fetch tools
Tools that can be used to fetch data directly
1. `get_ramp_categories`
2. `get_currencies`#### Load tools
Loads data to server which the client can fetch. Based on the tools you wish to use, ensure to enable those scopes on your
Ramp client and include the scopes when starting the server as a CLI argument.| Tool | Scope |
| ------------------------- | ------------------- |
| load_transactions | transactions:read |
| load_reimbursements | reimbursements:read |
| load_bills | bills:read |
| load_locations | locations:read |
| load_departments | departments:read |
| load_bank_accounts | bank_accounts:read |
| load_vendors | vendors:read |
| load_vendor_bank_accounts | vendors:read |
| load_entities | entities:read |
| load_spend_limits | limits:read |
| load_spend_programs | spend_programs:read |
| load_users | users:read |For large datasets, it is recommended to explicitly prompt Claude not to use REPL and to keep responses concise to avoid timeout or excessive token usage.
## Setup
### Ramp Setup
1. Create a new client from the Ramp developer page (Profile on top right > Developer > Create app)
2. Grant the scopes you wish (based on tools) to the client and enable client credentials (Click on App > Grant Types / Scopes)
3. Include the client ID and secret in the config file as well as the scopes you wish to use### Local Setup
1. Clone this Github repo via `git clone [email protected]:ramp/ramp-mcp.git` or equivalent
2. Install [`uv`](https://docs.astral.sh/uv/)## Usage
Run the MCP server from your CLI with:
```bash
RAMP_CLIENT_ID=... RAMP_CLIENT_SECRET=... RAMP_ENV= uv run ramp-mcp -s
```## Configuration
### Usage with Claude Desktop
Add this to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"ramp-mcp": {
"command": "uv",
"args": [
"--directory",
"//ramp-mcp", // make sure to update this path
"run",
"ramp-mcp",
"-s",
"transactions:read,reimbursements:read"
],
"env": {
"RAMP_CLIENT_ID": "",
"RAMP_CLIENT_SECRET": "",
"RAMP_ENV": ""
}
}
}
}
```If this file doesn't exist yet, create one in `//Library/Application Support/Claude/`
## License
Copyright (c) 2025, Ramp Business Corporation
All rights reserved.
This source code is licensed under the MIT License found in the LICENSE file in the root directory of this source tree.