DevRev MCP Server

Official DevRev MCP server connecting AI agents to work items, parts, vistas, search, and the unified support, product, and engineering knowledge graph.

Developer Tools by DevRev OAuth2 active

Connect (Remote Server) GitHub Docs

Overview

DevRev is a developer-first CRM that unifies support, product, and engineering workflows on a single knowledge graph. The official DevRev MCP server exposes that graph to AI agents, letting them read and write work items (issues, tickets), parts (enhancements), vistas (sprint boards), meetings, and timeline entries, and run hybrid search across articles, tickets, accounts, rev_orgs, and other DevRev objects.

DevRev publishes the server in two forms. The recommended option is the hosted remote MCP server at https://api.devrev.ai/mcp/v1, which supports OAuth in clients like Claude Desktop and Cursor, and Personal Access Token auth for Claude Code and CLI tools. There is also an open-source Python implementation at github.com/devrev/mcp-server distributed as the devrev-mcp package, runnable via uvx with a DEVREV_API_KEY environment variable.

Because DevRev already ingests data from systems like Jira, Zendesk, GitHub, and Salesforce, the MCP server acts as a gateway to a pre-integrated context layer. Agents can answer multi-hop questions (for example, linking a customer ticket to the underlying product issue and the sprint it lives in) without orchestrating separate integrations.

Tools

Tool	Description
`search`	Hybrid search across DevRev namespaces (articles, issues, tickets, parts, dev_users, accounts, rev_orgs, vistas, incidents).
`get_work`	Fetch a specific DevRev work item (issue or ticket) by ID with full details.
`create_work`	Create a new issue or ticket with title, body, assignees, and associated parts.
`update_work`	Update an existing work item's title, body, assignees, parts, or stage.
`list_works`	List and filter work items by state, dates, assignees, parts, and other criteria.
`get_part`	Get details about a specific part (enhancement) by ID.
`create_part`	Create a new part with name, description, assignees, and parent part.
`update_part`	Update a part's name, description, assignees, target dates, or stage.
`list_parts`	List and filter parts by dates, assignees, parent parts, and more.
`get_current_user`	Return details about the currently authenticated DevRev user.
`get_vista`	Retrieve a vista (sprint board) by ID, including its vista group items (sprints).
`list_meetings`	List and filter meetings by channel, participants, dates, and meeting states.
`list_subtypes`	List available subtypes for a given leaf type (issue or ticket) for proper categorization.

Setup Guide

Prerequisites

A DevRev account (sign up at app.devrev.ai/signup)
Your DevRev organization slug (the path after https://app.devrev.ai/)
For PAT-based clients: a Personal Access Token from DevRev user settings

Option 1: Remote MCP server (recommended)

The hosted server lives at https://api.devrev.ai/mcp/v1.

Claude Code (PAT auth):

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

Claude Desktop / Cursor (OAuth): add the connector from the client's MCP directory and complete the OAuth flow, providing your DevRev org slug when prompted.

Generic client config (HTTP):

{
  "mcpServers": {
    "devrev": {
      "transport": "http",
      "url": "https://api.devrev.ai/mcp/v1",
      "headers": {
        "Authorization": "Bearer YOUR_DEVREV_PAT"
      }
    }
  }
}

Option 2: Open-source local server

Install via uvx and provide your API key:

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

Source: https://github.com/devrev/mcp-server

Use Cases

Triage inbound support tickets by searching past tickets, linked articles, and product issues for context, then drafting a reply or escalation.
Auto-create DevRev issues from customer tickets and link them to the correct part and current sprint vista.
Sprint planning assistants that list open work items by assignee and target dates, then move them between stages.
Build a customer health view by pulling related accounts, rev_orgs, tickets, and incidents through a single search call.
Generate weekly product status reports by listing recently updated parts, work items, and meetings.

Example Prompts

"Search DevRev for all open tickets mentioning 'SSO login failure' and summarize the top themes."
"Create a new DevRev issue titled 'Rate limit on /search endpoint' under the Search part and assign it to me."
"List all work items in the current sprint vista that are still in the In Progress stage."
"Find the ticket for Acme Corp's outage last week and link it to the underlying engineering issue."
"Show me my open tickets due this week and update the priority on the customer-impacting ones."

Pros

Officially maintained by DevRev with both a hosted remote MCP server and an open-source reference implementation.
Broad coverage across work items, parts, vistas, meetings, and search, not just CRUD on a single object type.
Hybrid search exposes the unified DevRev knowledge graph (tickets, issues, accounts, articles) through a single tool.
Supports OAuth for modern clients and PAT for CLI and headless setups.

Limitations

OAuth support is documented as alpha and may behave inconsistently across MCP clients.
Requires a DevRev account and ingested data to be useful, so it is not a quick win for teams not already on DevRev.
Tool surface is centered on DevRev primitives; deep workflow automations (custom stages, complex timeline entries) may still require direct API calls.

Alternatives

Linear MCP server for issue tracking focused workflows.
Jira MCP server (Atlassian Remote MCP) for teams on Atlassian.
Zendesk MCP integrations for support-only use cases without DevRev's unified graph.