As an agent-first platform, DevRev provides a remote MCP server for work with agentic platforms such as Claude desktop and Cursor.
The DevRev remote MCP server is available at https://api.devrev.ai/mcp/v1.
The MCP server currently supports two modes of authentication: OAuth or DevRev-generated PAT.
Most MCP clients (such as the Claude desktop) automatically use OAuth when connecting to the server, so no configuration is required.
We support a wide variety of MCP clients, most notable are the following:
The DevRev remote MCP Server also supports any local MCP-compatible client that can run on localhost and connect to the server via the mcp-remote proxy. This enables custom or third-party integrations that follow the MCP specification.
For detailed setup instructions, refer to your client's own MCP documentation or built-in assistant.
DevRev MCP server supports OAuth authentication in Claude Desktop and Cursor IDE. These clients complete authentication via a browser-based OAuth flow.
Claude Code does not support OAuth. When using Claude Code, you must authenticate using a personal access token (PAT), as described in the section below.
Installing a DevRev connector to Claude requires Admin permissions. You must first add the connector to your team; only then can team members connect to it.
OAuth authentication is available only in Claude (both the desktop and web apps).
In the Claude app, navigate to Settings > Connectors, then click Browse connectors and search for DevRev.
2. Select DevRev from the results and click Add to your team. The DevRev connector will appear in the list of available connectors. Click Connect to begin the setup process. A new browser tab opens, prompting you to enter your organization’s slug.
The slug is the string that follows https://app.devrev.ai/ in your DevRev URL. For example, if your URL is https://app.devrev.ai/acme/, the slug is acme.
Click Continue to proceed to the next step, where you must review and confirm the access permissions required by Claude.
After the connection is complete, the DevRev connector status changes to Connected. Clicking the connector shows additional details, including the list of available tools.
You can connect the DevRev MCP server to Cursor IDE using OAuth in two ways. Both methods ultimately require the same configuration and authentication steps.
Option 1: Add DevRev MCP from the Cursor Website
Install from Cursor’s MCP directory
Go to Cursor’s official MCP directory and locate the DevRev MCP server.
Click “+ Add to Cursor”.
Confirm installation in Cursor
Your browser will open Cursor IDE and display a confirmation modal.
Click Confirm / Install to proceed.
Initial connection attempt (expected to fail)
After installation, Cursor will automatically try to connect to the DevRev MCP server.
This connection will fail, because the required OAuth configuration is not yet complete.
Edit the MCP configuration
Click the Edit button for the DevRev MCP server.
Add your CLIENT_ID to the configuration file.
Example configuration:
{
"mcpServers": {
"DevRev": {
"url": "https://api.devrev.ai/mcp/v1",
"auth": {
"CLIENT_ID": "AB0hoKlvrU1rh3rBF4jkb2rbOd6T2qDR"
}
}
}
}Reconnect the server
Save the configuration and click Connect again.
Authenticate with DevRev
A browser window will open, prompting you to enter your DevRev organization slug.
Enter the slug and click Continue.
The slug is the string that follows https://app.devrev.ai/ in your DevRev URL. For example, if your URL is https://app.devrev.ai/acme/, the slug is acme.
Connection successful
You will be redirected back to Cursor IDE.
The DevRev MCP server will now show as connected, and all available DevRev tools will be accessible.
Open MCP settings in Cursor
In Cursor IDE, open Settings → Cursor Settings →Tools & MCP.
Add a custom MCP server
Click “Add Custom MCP”.
Provide the MCP configuration
Paste the same configuration shown below, making sure to include your CLIENT_ID:
{
"mcpServers": {
"DevRev": {
"url": "https://api.devrev.ai/mcp/v1",
"auth": {
"CLIENT_ID": "YOUR_CLIENT_ID_HERE"
}
}
}
}
Connect and authenticate
Click Connect.
A browser window will open asking for your DevRev organization slug.
Enter the slug and click Continue.
The slug is the string that follows https://app.devrev.ai/ in your DevRev URL. For example, if your URL is https://app.devrev.ai/acme/, the slug is acme.
Finish setup
After successful authentication, you will be redirected back to Cursor, and the DevRev MCP server will be connected and ready to use.
Once connected, you can immediately start using the DevRev MCP tools within Cursor IDE.
Claude Code currently only supports DCR OAuth flows, which presents a compatibility limitation with our existing authentication infrastructure. Until broader OAuth support is available in Claude Code, we recommend authenticating with our remote MCP server using a PAT.
For configuring PAT authentication with Claude Code, we recommend following their official docs here.
Below is a command for quick copying if you are already familiar with setting up MCP servers in Claude Code:
claude mcp add --transport http devrev https://api.devrev.ai/mcp/v1 \
--header "Authorization: Bearer <token>"Note: Claude code allows for scoped configurations. To avoid adding the MCP server in each Claude project/directory, append the --scope user option to the above command. More on scope configurations in Claude code can be found on their official page.
Cursor only allows OAuth for a curated list of MCP servers. Until DevRev is listed, PAT authentication is the only way to use the remote MCP through Cursor.
In Cursor, go to Preferences > Cursor settings and open the Tools & Integrations tab from the side menu.
Click Add Custom MCP or New MCP Server if you already have some registered.
Edit the mcp.json and add the following JSON object into it:
{
"mcpServers":{
"DevRev MCP":{
"url":"https://api.devrev.ai/mcp/v1",
"headers":{
"Authorization":"<token>"
}
},
}
}Save the file to apply the addition of the remote MCP server.