DevRev

You can run DevRev’s MCP Server to access and manage DevRev data—from work items and parts to meetings and sprint information—via a lightweight, local or remote MCP client. This server ties your client tools to DevRev APIs, enabling powerful, scriptable workflows across your projects.

How to use

Use an MCP client to connect to the DevRev MCP Server and perform common tasks: search across namespaces, manage work items (issues and tickets), create and update parts (enhancements), list meetings, and handle workflow details like valid stage transitions and timeline entries. Start by authenticating with your API key and selecting either the published or development MCP endpoint. Then use the client commands to fetch and manipulate data, filter results, and plan sprints with vista boards.

How to install

Prerequisites: you need a modern Python environment and a tool to run MCP servers. This guide assumes you will use uvx for production-ready runs or uv for development builds.

Install uvx or uv on your system.

# Install uvx (recommended for production)
curl -LsSf https://astral.sh/uv/install.sh | sh

# Alternatively, install uv (for development)
pip install uv
```} ,{

Configuration and running the server

The following configurations expose two ways to run the DevRev MCP Server. Use the published configuration for standard usage, or the development configuration when you are actively building or testing.

"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"
    }
  }
}
```"}]} ,{

Additional notes

Ensure your DEVREV_API_KEY is kept secret and only shared with trusted clients. If you are testing, consider using a separate development API key. The MCP server supports both published and development configurations, so you can switch between uvx and uv as needed.

Configuration details

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

Operational tools and endpoints

The server provides a rich set of endpoints for working with DevRev entities. You can search across namespaces, fetch current user data, access vista boards for sprint planning, manage work items and parts, handle meetings, validate stage transitions, add timeline entries, and retrieve subtypes for proper categorization.

Security and access

Treat your API key as a secret credential. Use secure storage for keys, rotate them regularly, and restrict access to clients that truly need to operate the MCP server.

Troubleshooting

If you encounter startup issues, verify that the API key is correctly set in the environment, confirm the path to the MCP directory exists for development runs, and ensure the terminal has the latest PATH updates after installation.

Available tools

search

Search across DevRev data using the hybrid search API with support for various namespaces such as articles, issues, tickets, parts, dev_users, accounts, rev_orgs, vistas, and incidents.

get_current_user

Retrieve details about the currently authenticated DevRev user.

get_vista

Fetch information about a vista (sprint board) by its ID, including associated sprints.

get_work

Obtain full details for a specific work item (issue or ticket) by its ID.

create_work

Create a new work item with properties like title, body, assignees, and related parts.

update_work

Modify an existing work item, including its title, body, assignees, parts, or stage transitions.

list_works

List and filter work items by state, dates, assignees, parts, and more.

get_part

Fetch detailed information for a specific part (enhancement) by its ID.

create_part

Create a new part with properties such as name, description, assignees, and parent parts.

update_part

Update an existing part, including name, description, assignees, target dates, or stage transitions.

list_parts

List and filter parts by dates, assignees, parent parts, and other criteria.

list_meetings

List and filter meetings across channels with date and participant-based filtering.

valid_stage_transition

Provide a list of valid stage transitions for a given work item or part to ensure transitions are allowed.

add_timeline_entry

Append timeline entries to track updates and progress on works or parts.

get_sprints

Retrieve active or planned sprints for a given part to assist planning and assignment.

list_subtypes

List all available subtypes for a leaf type (issue or ticket) to enable proper categorization.