DevRev MCP Server

DevRev MCP Server

What is DevRev MCP Server about?

DevRev MCP Server exposes a full‑featured Model Context Protocol interface to DevRev’s platform. It lets clients interact programmatically with work items (issues, tickets), parts (enhancements), vista boards, meetings, user information, and sprint planning, all through a single, consistent server.

How to use DevRev MCP Server?

1. Install the runtime – install uv (or uvx) as described in the README.
2. Configure the API key – set DEVREV_API_KEY in the environment with a personal access token.
3. Run the server – use the provided command configuration (e.g., uvx devrev-mcp).
4. Call MCP methods – invoke the exposed tools such as search, list_works, create_part, get_vista, etc., using the MCP client of your choice.

Key features of DevRev MCP Server

• CRUD operations for issues, tickets, and parts with hierarchical relationships.
• Hybrid search across multiple namespaces (articles, issues, tickets, parts, users, accounts, vistas, incidents).
• Vista board integration for sprint and group‑item retrieval.
• Advanced filtering, pagination, and custom field support for listing resources.
• Workflow utilities: stage‑transition validation, timeline entry creation.
• Meeting enumeration with channel and state filters.
• Subtype enumeration for proper categorization of issues/tickets.
• User context retrieval via get_current_user.

Use cases of DevRev MCP Server

• Automated ticket triage: Sync external bug trackers and create DevRev tickets automatically.
• Sprint planning dashboards: Pull Vista sprint data to build custom planning UI.
• Analytics & reporting: Run complex searches and aggregate work‑item metrics.
• Integration with CI/CD: Update work‑item stages based on deployment pipelines.
• Meeting minutes automation: List meetings and attach notes via timeline entries.

FAQ from the DevRev MCP Server

• Do I need Python to run the server? Yes, the server runs on Python and uses uv/uvx for execution.
• Which environment variable holds the API token? DEVREV_API_KEY.
• Can I run the server locally for development? Yes, use the uv command with the --directory argument pointing to the source folder.
• Is pagination handled automatically? The server provides pagination parameters; clients must request subsequent pages as needed.
• What if I encounter a "command not found" error for uv? Verify the installation directory (typically ~/.cargo/bin/) is in your PATH and restart the terminal.

DevRev MCP Server

Overview

A Model Context Protocol server for DevRev. This server provides comprehensive access to DevRev's APIs, allowing you to manage work items (issues, tickets), parts (enhancements), meetings, workflow transitions, timeline entries, sprint planning, and subtypes. Access vista boards, search across your DevRev data, and retrieve user information with advanced filtering and pagination support.

Tools

Search & Discovery

• search: Search for information across DevRev using the hybrid search API with support for different namespaces (articles, issues, tickets, parts, dev_users, accounts, rev_orgs, vistas, incidents).
• get_current_user: Fetch details about the currently authenticated DevRev user.
• get_vista: Retrieve information about a vista (sprint board) in DevRev using its ID. Vistas contain sprints (vista group items) that can be used for filtering and sprint planning.

Work Items (Issues & Tickets)

• get_work: Get comprehensive information about a specific DevRev work item using its ID.
• create_work: Create new issues or tickets in DevRev with specified properties like title, body, assignees, and associated parts.
• update_work: Update existing work items by modifying properties such as title, body, assignees, associated parts, or stage transitions.
• list_works: List and filter work items based on various criteria like state, dates, assignees, parts, and more.

Parts (Enhancements)

• get_part: Get detailed information about a specific part (enhancement) using its ID.
• create_part: Create new parts (enhancements) with specified properties including name, description, assignees, and parent parts.
• update_part: Update existing parts by modifying properties such as name, description, assignees, target dates, or stage transitions.
• list_parts: List and filter parts based on various criteria like dates, assignees, parent parts, and more.

Meetings & Communication

• list_meetings: List and filter meetings in DevRev based on various criteria such as channel, participants, dates, and meeting states.

Workflow Management

• valid_stage_transition: Get a list of valid stage transitions for a given work item (issue, ticket) or part (enhancement). Use this before updating stages to ensure transitions are valid.
• add_timeline_entry: Add timeline entries to work items (issues, tickets) or parts (enhancements) to track updates and progress.
• get_sprints: Get active or planned sprints for a given part ID, useful for sprint planning and issue assignment.
• list_subtypes: List all available subtypes in DevRev for a given leaf type (issue or ticket), enabling proper categorization of work items.

Prerequisites

Before using this MCP server, you need to install either uvx or uv, which are modern Python package and project management tools.

Installing uv (Recommended)

uv is a fast Python package installer and resolver. It includes uvx for running Python applications.

On macOS and Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

On Windows:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Alternative Installation Methods:

Using Homebrew (macOS):

brew install uv

Using pip:

pip install uv

Verifying Installation

After installation, verify that uv and uvx are available:

# Check uv version
uv --version

# Check uvx version  
uvx --version

Both commands should return version information. If you get "command not found" errors, you may need to restart your terminal or add the installation directory to your PATH.

Troubleshooting

If you encounter issues:

1. Restart your terminal after installation
2. Check that the installation directory is in your PATH
3. On macOS/Linux, the default installation adds uv to ~/.cargo/bin/
4. Refer to the official uv documentation for more detailed installation instructions

Configuration

Get the DevRev API Key

1. Go to https://app.devrev.ai/signup and create an account.
2. Import your data from your existing data sources like Salesforce, Zendesk while following the instructions here.
3. Generate an access token while following the instructions here.

Usage with Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows: %APPDATA%/Claude/claude_desktop_config.json

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

"mcpServers": {
  "devrev": {
    "command": "uv",
    "args": [
      "--directory",
      "Path to src/devrev_mcp directory",
      "run",
      "devrev-mcp"
    ],
    "env": {
      "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY"
    }
  }
}

Features

• Comprehensive Work Item Management: Create, read, update, and list both issues and tickets with advanced filtering
• Enhanced Part Management: Full CRUD operations for parts (enhancements) including hierarchical relationships
• Advanced Search: Search across multiple namespaces (articles, issues, tickets, parts, dev_users, accounts, rev_orgs, vistas, incidents) with hybrid search capabilities
• Vista Board Integration: Access vista (sprint board) information and retrieve sprint group items for effective sprint management
• Flexible Filtering: Advanced filtering options for listing work items and parts based on dates, assignees, states, custom fields, subtypes, and more
• User Context: Access to current user information for personalized experiences
• Rich Data Support: Handle complex relationships between work items, parts, users, organizations, and sprints
• Meeting Management: List and filter meetings across different channels and states with comprehensive date filtering
• Workflow Control: Validate stage transitions and manage work item lifecycle with precise stage management
• Timeline Tracking: Add timeline entries to track progress and updates on work items and parts
• Sprint Planning: Access sprint information for effective project management and issue assignment with vista integration
• Subtype Management: List and manage subtypes for proper categorization of issues and tickets