title: Developer MCP source_url: /developer-api/v1/developer-mcp summary: The Developer MCP server is subject to change. Feedback and questions can be submitted via a Developer API support ticket. content: The Developer MCP server is subject to change. Feedback and questions can be submitted via a Developer API support ticket. Developer MCP is Ramp's unauthenticated Model Context Protocol server for developers building with Ramp's API. It gives AI assistants live access to Ramp's developer documentation, API reference, and OpenAPI schemas directly inside your coding workflow. Unlike Ramp MCP servers that access account data, Developer MCP does not require a Ramp account, OAuth login, API key, or developer app. It only serves public Ramp Developer API documentation. Why use Developer MCP? Developer MCP reads from Ramp's published developer docs and OpenAPI exports, so assistants can look up current guides, endpoint reference material, request bodies, response shapes, and parameter definitions. Ask for an endpoint by operation ID, docs URL, HTTP method and path, or natural selector. Developer MCP can return the matching OpenAPI operation, including request and response schemas. Use Developer MCP to answer implementation questions without leaving your editor: authentication setup, pagination, webhooks, required fields, endpoint behavior, and schema details. Getting started Server URL: https://mcp.ramp.com/developer/mcp Open Claude Desktop Navigate to Settings → Developer Click 'Edit config' Add the Developer MCP server: Restart Claude Desktop — Developer MCP works without authentication. Add the Developer MCP server to your Claude Code session: Then run /mcp in your Claude Code session to activate the server and start asking API questions. Cursor Desktop App Required The Cursor desktop app must be installed for this one-click link to work. Add the Developer MCP server to your VS Code MCP settings: Add the Developer MCP server to your Codex CLI configuration (~/.codex/config.toml): Or add it from the terminal: For clients supporting remote MCP connections, use the server URL: https://mcp.ramp.com/developer/mcp Refer to your client's MCP documentation for specific configuration steps. Available tools Developer MCP exposes documentation tools backed by Ramp's public Developer Docs API. Search Ramp Developer API guides and endpoint reference content. Use this first for broad questions like OAuth setup, pagination, webhooks, or finding the right endpoint. Results can include guide pages and API operations. API results include fields like operation_id, method, endpoint_path, and docs_url. Return the OpenAPI operation object for one endpoint. You can select an operation by: Examples: If a selector is ambiguous, the tool returns matching operations so the assistant can retry with a more specific operation ID or method + path. Resolve a pasted docs artifact to a canonical guide, file, directory, or API operation. Accepted inputs include docs URLs, guide slugs, virtual paths, operation IDs, METHOD /developer/v1/..., and bare endpoint paths. If the resolved artifact is a directory, use developer_docs_list with the returned path to browse its children. Read one exported docs file by virtual path. The response includes the file body plus available metadata such as title, source URL, and content type. List files and directories in the docs virtual filesystem. Useful for browsing guide exports under paths like: Return the docs API root index and top-level directories. This is mainly useful when an assistant needs to orient itself before browsing or reading files. Submit feedback about Developer MCP, Ramp's API docs, or confusing tool results. Use this to report missing docs, incorrect schemas, unexpected behavior, or suggestions for improving the developer experience. Recommended workflow Search with developer_docs_search Read the most relevant guide with developer_docs_read Use developer_docs_schema when exact request or response fields are needed Search by topic or endpoint name Pass the returned operation_id into developer_docs_schema If the schema contains $ref values, read /openapi/developer-api.json with developer_docs_read to resolve shared components Use developer_docs_resolve If the result is a guide or file, use developer_docs_read If the result is an API operation, use developer_docs_schema Troubleshooting Configuration not working: Verify JSON syntax in configuration files Ensure file paths are correct for your operating system Restart your client after making configuration changes Node.js or npm issues: Ensure Node.js is properly installed Try npm install -g mcp-remote to install the required package Remote MCP connection issues: Remote MCP connections are early technology. If connection fails, restart your client and try again Ensure your client supports HTTP-based MCP connections Ambiguous endpoint result: Retry with both HTTP method and path, for example DELETE /developer/v1/bills/{bill_id} Or use the returned operation_id directly with developer_docs_schema No useful search results: Search with more specific terms Use scope=/api for endpoint searches Use scope=/guides for prose documentation searches Schema contains $ref: Read /openapi/developer-api.json with developer_docs_read Resolve references against #/components/schemas/... Support: Submit a Developer API support ticket Feedback Tool: Use developer_submit_feedback directly within the MCP interface