DevRev MCP Server

About

The DevRev MCP Server lets MCP-capable clients like Claude Desktop, Cursor, and Windsurf search and manage DevRev's unified customer-and-dev platform directly from chat, without switching to the DevRev web app. Its search tool queries across multiple DevRev namespaces at once — issues, tickets, articles, and more — using DevRev's own query syntax (e.g. `product:payments api` scopes a search to a specific product part), so an agent can locate relevant work items in one call instead of paging through separate endpoints. Work-item tools cover listing works filtered by type/owner/related-part, fetching full object detail by ID, and creating new issues or tickets tied to a specific feature or part — useful for turning a bug report surfaced in a support ticket into a linked engineering issue without leaving the assistant. Parts-management tools expose the product hierarchy (products, capabilities, features, epics) so an agent can navigate DevRev's org structure, and a built-in devrev_context() tool returns comprehensive documentation on every available tool, namespace, and parameter — handy for self-onboarding an agent into an unfamiliar DevRev workspace. Authentication uses a DevRev Personal Access Token set as the DEVREV_API_KEY environment variable; the server runs as a local Python process (SSE transport on 127.0.0.1:8888 by default) that Cursor or another client connects to over HTTP. This is an unofficial, community-maintained implementation — DevRev itself has not published a first-party MCP server as of this writing — so treat it as the best available option for AI-assisted DevRev workflows rather than a vendor-supported integration.

Installation

git clone https://github.com/KalshuCodes/devrev-mcp-server && cd devrev-mcp-server && ./install.sh

Categories

Works With

Frequently Asked Questions