DevRev MCP server

What is DevRev MCP server?

A Model Context Protocol server for DevRev that enables searching and retrieving information from DevRev using its APIs.

How to use DevRev MCP server?

Generate a DevRev API key from your DevRev account, then configure the server in Claude Desktop by adding a devrev entry under mcpServers in the configuration file, setting the DEVREV_API_KEY environment variable.

Key features of DevRev MCP server

• Search DevRev data using the search tool
• Retrieve full details of a DevRev object by ID with get_object
• Integrates with Claude Desktop via the MCP protocol
• Supports both published (uvx) and development (uv) run modes
• Uses a personal access token for authentication
• Works with data imported from Salesforce, Zendesk, and other sources

Use cases of DevRev MCP server

• Querying DevRev knowledge base or issue tracker via natural language
• Looking up a specific DevRev object (e.g., a ticket or account) without leaving the chat
• Automating information retrieval from DevRev during conversations in Claude Desktop

FAQ from DevRev MCP server

What is the DevRev API key and how do I get one?

The API key is a personal access token generated from the DevRev developer portal (https://developer.devrev.ai/public/about/authentication#personal-access-token-usage). You first need a DevRev account and you can import your data from sources like Salesforce or Zendesk.

How do I run the DevRev MCP server with Claude Desktop?

You add a configuration entry in Claude Desktop's claude_desktop_config.json file. For the published version, use "command": "uvx" with "args": ["devrev-mcp"] and set the DEVREV_API_KEY environment variable. For a development version, use "command": "uv" with the path to the source directory.

What tools does the DevRev MCP server provide?

Two tools: search to run searches against the DevRev search API with a query and namespace, and get_object to retrieve all information about a DevRev object by its ID.

Where does my data live when using this server?

The server interacts with DevRev’s APIs—your data remains in the DevRev platform and is accessed via API calls; the server does not store or cache data locally.

Does the server require any other dependencies?

For the published version, it runs via uvx. For development, it requires uv and a local copy of the source code. No additional runtime dependencies are mentioned.