Ramp MCP
# Ramp MCP
Simple MCP server that interfaces with the Ramp API, allowing you to talk to your Ramp data from any MCP client like Cursor or Claude Desktop.
I am adding more coverage of the Ramp API over time, let me know which tools you need or just open a PR.
## Installation
Make sure to go to your Ramp Settings to get a [Ramp API Key and Ramp Client ID](https://app.ramp.com/settings/ramp-developer).
### Installing via Smithery
To install mercury-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@dragonkhoi/mercury-mcp):
```bash
npx -y @smithery/cli install @dragonkhoi/mercury-mcp --client claude
```
To install mixpanel-mcp for Cursor, go to Settings -> Cursor Settings -> Features -> MCP Servers -> + Add
Select Type: command and paste the below, using the arguments `<API_KEY> <CLIENT_ID>` from Ramp
```
npx -y @smithery/cli@latest run @dragonkhoi/mercury-mcp --config "{\"mercury_api_key\":\"YOUR_MERCURY_API_KEY\",}"
```
### Clone and run locally
Clone this repo
Run `npm run build`
Paste this command into Cursor (or whatever MCP Client)
`node /ABSOLUTE/PATH/TO/ramp-mcp/build/index.js RAMP_API_KEY RAMP_CLIENT_ID`
## Examples
Ask "What are my latest credit card transactions"
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves credit card transactions, while the other retrieves statements with filtering capabilities. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the need.
Both tools follow a consistent verb_noun naming pattern (get_credit_card_transactions and get_ramp_statements), using the same verb 'get' and snake_case formatting. This predictability aids in tool identification and usage.
With only two tools, the server feels under-scoped for a financial management domain like Ramp, which typically involves more operations such as creating transactions, updating details, or managing accounts. The limited set may hinder comprehensive agent workflows.
The tool surface is severely incomplete for a Ramp integration, covering only retrieval of transactions and statements. Missing are essential CRUD operations (e.g., create, update, delete), account management, or other financial actions, leading to significant gaps that will cause agent failures in broader tasks.