devrev

This MCP server integrates with DevRev APIs to provide a searchable knowledge interface and object retrieval capabilities. It exposes two tools: search, which queries DevRev across available namespaces using a given query, and get_object, which fetches all information about a DevRev object by its ID. To use it, configure the MCP server in your Claude/CLI environment (as shown in the published configuration) and call the tools with appropriate arguments. For search, supply a query string and, optionally, a namespace to narrow results. For get_object, supply the DevRev object ID to retrieve its full details.

Typical workflows include: (1) Searching for documents, tickets, or objects related to a topic, then (2) retrieving a specific object by ID to inspect all metadata and linked information. The server authenticates with DevRev via a personal access token provided in the DEVREV_API_KEY environment variable. Keep this key secure and do not expose it in transcripts. If you switch between published (uvx) and development/unpublished (uv) configurations, ensure the correct command and directory arguments are used and that the API key is present in the environment for both modes.

Prerequisites

• Access to a DevRev account and a DevRev API key (DEVREV_API_KEY).
• A host machine with Python and/or the MCP execution environment that supports uv/uvx commands as configured by Claude/Desktop integration.
• Optional: Claude Desktop configured for MCP servers as shown in the provided configuration snippet.

Installation steps

1. Obtain your DevRev API key by signing up and generating a personal access token as described in the project README.

2. Decide whether you will use the published server configuration (uvx) or the development/unpublished configuration (uv). The provided configuration uses uvx with the devrev-mcp package directory:

   • Published server (uvx):

     • Command: uvx
     • Args: ["devrev-mcp"]
     • Env: { "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY" }

   • Development/Unpublished server (uv):

     • Command: uv
     • Args: ["--directory", "Path to src/devrev_mcp directory", "run", "devrev-mcp"]
     • Env: { "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY" }

3. If using Claude Desktop, update the Published Servers Configuration or Development configuration block with your API key and the appropriate path for the devrev-mcp directory if using the development setup. For example:

   Published: { "mcpServers": { "devrev": { "command": "uvx", "args": ["devrev-mcp"], "env": { "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY" } } } }

4. Install and run the MCP server according to your environment. If you are using the development setup, ensure the path to the src/devrev_mcp directory is correct in the arguments.

5. Verify connectivity by running a quick test query against the server using the search tool and a sample query (e.g., a topic related to your data) and then fetch an object by ID to confirm get_object works as expected.

Tips and common issues:

• Ensure DEVREV_API_KEY is kept secret and not exposed in logs or transcripts.
• If you switch between published (uvx) and development (uv) modes, make sure the corresponding directory path and command are correctly set in your configuration.
• DevRev API keys may have permissions and rate limits; monitor usage to avoid hitting limits during bursts of activity.
• If the server fails to authenticate, double-check the environment variable name and value, and ensure there are no stray spaces or newline characters.
• The tools rely on the DevRev API; if DevRev changes their API, you may need to update the underlying MCP implementation to stay compatible.