DevRev MCP server: Connect your AI coding assistant

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.

Supported clients

We support a wide variety of MCP clients, including the following:

• OpenAI ChatGPT/Codex

• Claude Code (PAT only)

• Claude Desktop

• GitHub Copilot CLI

• Google Gemini

• Amazon Quick Suite

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.

Authenticate with OAuth

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.

Configure for Claude Desktop

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).

1. 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.

1. 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.

Configure for Cursor

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

1. Install from Cursor’s MCP directory
   Go to Cursor’s official MCP directory and locate the DevRev MCP server.
   Click “+ Add to Cursor”.

   

2. Confirm installation in Cursor
   Your browser will open Cursor IDE and display a confirmation modal.
   Click Confirm / Install to proceed.

   

3. 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.

   

4. 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"
         }
       }
     }
   }

5. Reconnect the server
   Save the configuration and click Connect again.

6. 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.

   

7. 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.

   

Option 2: Add DevRev MCP manually from Cursor IDE

1. Open MCP settings in Cursor
   In Cursor IDE, open Settings → Cursor Settings →Tools & MCP.

2. Add a custom MCP server
   Click “Add Custom MCP”.

   

3. 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"
         }
       }
     }
   }
   

4. 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.

5. 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.

Authenticate with a PAT

If your MCP client does not support OAuth, you can authenticate with a personal access token (PAT) instead. To generate a PAT, see Authentication.

📝 Note: OAuth is the preferred authentication method. Use a PAT only when your client lacks OAuth support or when OAuth is not yet compatible with the DevRev MCP server for that client.

Configure for Claude Code

Claude Code supports only DCR-based OAuth flows—a protocol where the client registers itself automatically with the authorization server. The DevRev MCP server does not yet support this registration protocol, so Claude Code cannot complete OAuth with DevRev. Use a PAT as a fallback.

For full details, see the Claude Code MCP documentation.

Run the following command to add the DevRev MCP server:

claude mcp add --transport http devrev https://api.devrev.ai/mcp/v1 \
  --header "Authorization: Bearer <token>"

Replace <token> with your PAT.

📝 Note: Claude Code allows scoped configurations. To avoid adding the MCP server in every project directory, append --scope user to the command above. See Configuration scopes for details.

Configure for Codex

Codex does not support connecting to remote MCP servers natively. Use the mcp-remote proxy to bridge the connection.

1. Install the mcp-remote package globally with npm:

   npm install -g mcp-remote

2. Add the following entry to your Codex MCP configuration file so that mcp-remote proxies requests to the DevRev MCP server. Replace <token> with your PAT:

   {
     "mcpServers": {
       "DevRev MCP": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://api.devrev.ai/mcp/v1",
           "--header",
           "Authorization: Bearer <token>"
         ]
       }
     }
   }

3. Save the configuration file and restart Codex to apply the changes.

For additional guidance, see the Codex MCP documentation.

Configure for Cursor

Cursor allows OAuth only for a curated list of MCP servers. Until DevRev is included in that list, use a PAT to authenticate.

1. In Cursor, go to Preferences > Cursor settings and open the Tools & Integrations tab from the side menu.

2. Click Add Custom MCP (or New MCP Server if you already have servers registered), then edit the mcp.json file and add the following object. Replace <token> with your PAT:

   {
     "mcpServers": {
       "DevRev MCP": {
         "url": "https://api.devrev.ai/mcp/v1",
         "headers": {
           "Authorization": "Bearer <token>"
         }
       }
     }
   }

3. Save the file to apply the new MCP server configuration.