DevRev MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search DevRev using the provided query |
| get_objectB | Get all information about a DevRev object using its ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_object retrieves a specific object by ID, while search performs a broader query-based lookup. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb-based naming pattern (get_ and search), with clear, descriptive names that align well with their functions. No deviations or mixed conventions are present.
With only two tools, the server feels severely under-scoped for a DevRev platform, which typically involves objects like issues, tickets, or users. This minimal set lacks essential CRUD operations (e.g., create, update, delete) and limits agent functionality.
The tool surface is severely incomplete for a DevRev domain, offering only retrieval and search capabilities. There are no tools for creating, updating, or deleting objects, which are fundamental operations in such systems, leading to significant gaps in agent workflows.