Skip to main content
Glama
enesjakozh
kpsunil97

DevRev MCP Server

by kpsunil97
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

DevRev MCP server

Overview

A Model Context Protocol server for DevRev. It is used to search and retrieve information using the DevRev APIs.

Related MCP server: Scrapeless MCP Server

Tools

  • search: Search for information using the DevRev search API with the provided query and namespace.

  • get_object: Get all information about a DevRev object using its ID.

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"
    }
  }
}

Available Tools

2 tools
get_objectB

Get all information about a DevRev object using its ID

ParametersJSON Schema
NameRequiredDescriptionDefault
idYes

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states this is a read operation ('Get'), but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'all information' entails. For a tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a simple tool, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is minimal. It states the basic action but lacks details on return values, error cases, or operational context. Without annotations or output schema, the description should provide more completeness for effective use, but it falls short.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds meaning by specifying that the 'id' parameter is for a 'DevRev object,' which clarifies the context beyond the schema's generic string type. However, it doesn't detail format, constraints, or examples, leaving some ambiguity. With one parameter, the baseline is higher, but incomplete coverage limits the score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('DevRev object') with the specific mechanism ('using its ID'). It distinguishes from the sibling 'search' tool by focusing on retrieval by ID rather than searching. However, it doesn't specify what type of information is returned beyond 'all information,' which keeps it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a specific object ID, contrasting with the 'search' sibling for broader queries. However, it lacks explicit guidance on when to use this versus alternatives, prerequisites, or exclusions, leaving usage context somewhat inferred rather than clearly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • Addedget_object
    • Addedsearch
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Expert Server

    crazyrabbitLTC
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server utilizing Claude AI for generating intelligent queries and offering documentation assistance based on API documentation analysis.
    19
    3
    MIT
  • CodeAlive MCP by CodeAlive-AI

    CodeAlive MCPofficial

    CodeAlive-AI
    A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
    89
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kpsunil97/devrev-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server