Ramp Developer MCP Server
A local Model Context Protocol (MCP) server that provides AI assistants with access to Ramp's developer documentation, API schemas, and development guidance. This server enables natural language queries about Ramp's API endpoints, authentication methods, data relationships, and implementation patterns. Built specifically for developers building on Ramp's platform, it serves as an intelligent companion for API integration and development workflows. The server runs locally and processes Ramp's comprehensive developer documentation to provide contextual, accurate responses about API usage and best practices.
Example Queries and Use Cases
API Development
- "How do I authenticate with the Ramp API?"
- "Show me the schema for the cards endpoint"
- "What are the required fields for creating a new user?"
- "How do I handle rate limiting in the Ramp API?"
Data Relationships
- "How are cards related to users in the API?"
- "What's the relationship between transactions and bills?"
- "Show me how to link a purchase order to a bill"
Implementation Guidance
- "What are the best practices for handling webhooks?"
- "How do I implement single-use card creation?"
- "What scopes do I need for bill management?"
- "How should I structure pagination for large datasets?"
Troubleshooting
- "Why am I getting a 403 error on the users endpoint?"
- "What's the proper format for monetary values?"
- "How do I debug failed API requests?"
Available Tools
Core Tools
ping
- Test server connectivity and healthsearch_documentation
- Search through Ramp's developer documentation for specific topics, endpoints, or conceptsget_endpoint_schema
- Retrieve detailed OpenAPI schema information for specific Ramp API endpointssubmit_feedback
- Submit feedback about the MCP server or Ramp API development experience
Documentation Coverage
The server includes comprehensive documentation for:
- Authentication & Authorization - OAuth flows, API keys, scopes
- API Endpoints - Cards, users, bills, transactions, transfers, and more
- Data Relationships - How different Ramp entities connect
- Rate Limiting - Request limits and best practices
- Webhooks - Event handling and security
- Error Handling - Common errors and debugging approaches
- Monetary Values - Proper formatting and precision
- Pagination - Handling large result sets
- Category Codes - Spending categories and classifications
How to Use
Prerequisites
- Python 3.8+ with
uv
package manager - MCP-compatible client (Claude Desktop, Claude Code, or other MCP client)
- Git for cloning the repository
Setup Instructions
- Clone the repository:
- Install dependencies:
- Test the server:The server should start and display initialization messages.
Claude Desktop Configuration
- Locate your configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the server configuration:Option 1: Full path configuration (recommended):Option 2: Simple configuration (if
uv
is in your PATH):Configuration notes:- Replace
/path/to/ramp-dev-mcp
with the actual path where you cloned the repository - Replace
/Users/yourusername/.local/bin/uv
with your actualuv
installation path - To find your
uv
path, run:which uv
in your terminal - If
uv
is not in your PATH, use the full path configuration
- Replace
- Restart Claude Desktop
Claude Code Configuration
Other MCP Clients
For other MCP-compatible clients, configure them to run:
From the project directory.
Getting Started
Once configured, you can start asking questions like:
- "How do I create a new card using the Ramp API?"
- "What's the schema for the bills endpoint?"
- "Show me documentation about webhook security"
- "How do I handle rate limiting?"
The AI assistant will use the MCP server to search documentation, retrieve schemas, and provide accurate, contextual answers about Ramp API development.
Troubleshooting
Server fails to start:
- Ensure Python 3.8+ is installed
- Run
uv sync
to install dependencies - Check that you're in the correct directory
Configuration not working:
- Verify the file path in your MCP client configuration
- Ensure JSON syntax is correct
- Restart your MCP client after configuration changes
Getting help:
- Use the
submit_feedback
tool to report issues - Check the console output for error messages
- Ensure all dependencies are properly installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
Enables AI assistants to access Ramp's developer documentation and API schemas through natural language queries. Provides contextual answers about API endpoints, authentication methods, data relationships, and implementation patterns for developers building on Ramp's platform.
Related MCP Servers
- -securityFlicense-qualityEnables AI assistants to enhance their responses with relevant documentation through a semantic vector search, offering tools for managing and processing documentation efficiently.Last updated -938TypeScript
- AsecurityFlicenseAqualityProvides AI assistants like Claude or Cursor with access to Payman AI's documentation, helping developers build integrations more efficiently.Last updated -5TypeScript
- AsecurityFlicenseAqualityProvides AI assistants with access to Payman's documentation, helping developers build integrations more efficiently through enhanced contextual support.Last updated -5TypeScript
- -securityFlicense-qualityEnables AI assistants to search documentation of packages and services to find implementation details, examples, and specifications.Last updated -Python