DevRev

Search a DevRev workspace and create or update issues and tickets.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the DevRev connector does

The DevRev MCP server connects a DevRev workspace — a combined CRM, customer-support and issue-tracking platform — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 14 tools that search the knowledge graph and create or update issues, tickets and enhancements. Sign-in is OAuth, or a personal access token where a client cannot do OAuth.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

DevRev tools (14)

  • create_issue
  • update_issue
  • get_issue
  • list_issues
  • create_ticket
  • update_ticket
  • get_ticket
  • get_enhancement
  • update_enhancement
  • list_enhancements
  • get_part
  • hybrid_search
  • get_org_user
  • fetch_object_context

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No application scopes exist. DevRev's authorization server advertises 14 scopes, all OpenID identity claims, and the RFC 9728 resource descriptor declares no scopes_supported at all. Nothing at the OAuth grant separates reading from writing. DevRev's REST documentation defines per-object scopes such as ticket read, write and all, but those are API-level and are not offered as choices at MCP consent.
  • DevRev publishes no tool list for this server. The 14 names come from Anthropic's directory. We could not diff them against a vendor enumeration because none exists.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.
  • DevRev documents its own accuracy problem. Its engineering blog reports running the same query against the local and remote servers and getting a wrong answer from the remote one — "not with an error, but with a wrong answer" — attributing it to the size of the hybrid search schema. It states plainly that MCP "is not always the fastest, most accurate way of getting information". Verify what the agent reports before acting on it.
  • Custom fields inflate schemas. DevRev describes one customer with over 200 custom fields on the contact object alone, and says accuracy fell as tool schemas grew. A heavily customised workspace is the case where this connector performs worst.
  • Rate limits apply per user across all APIs, in a window resetting every five minutes, surfaced as HTTP 429 with Retry-After.
  • The MCP setup URL in DevRev's own blog is dead. That post directs readers to developer.devrev.ai/mcp for setup details; that path returned 404 on 2026-08-21. The working documentation is the support article linked below.
  • Whether a ticket write notifies the customer is unresolved. We found no DevRev documentation stating whether creating a ticket or changing its stage sends the customer an email, and we did not test it. Treat it as unknown rather than as a no.

Frequently asked questions

Can the DevRev connector post a reply that the customer sees?

Not with the 14 tools Anthropic lists. None of them writes a timeline comment, which is how DevRev posts a reply on a ticket. The write tools create and update issues and tickets, and a ticket body is customer-facing where the ticket is. DevRev's own predecessor package did ship a comment tool, so treat the absence as this listing's state rather than a guarantee.

What OAuth permissions does the DevRev MCP server request?

None that narrow anything. DevRev's authorization server advertised 14 scopes on 2026-08-21 and every one is an OpenID identity claim such as openid, profile, email and phone. The server's own RFC 9728 descriptor omits scopes_supported entirely. So the consent screen offers no way to grant reading a ticket without also granting updating one.

How many tools does the DevRev MCP server actually have?

Fourteen is a floor, not a total. DevRev publishes no tool list for the remote server, so the 14 come from Anthropic's directory. DevRev's engineering blog states teams can write TypeScript snap-ins, mark them as MCP tools, and have the schema merged into their org's server automatically. Your workspace may therefore expose tools nobody outside it can enumerate.

Why does Claude Code fail to sign in to DevRev with OAuth?

Because DevRev does not support the registration protocol Claude Code requires. DevRev's support article states Claude Code supports only DCR-based OAuth flows, where the client registers itself automatically with the authorization server, and that DevRev's MCP server does not yet support it. The documented workaround is to authenticate with a personal access token instead.

What personal data can the DevRev connector read?

Customer contact records and support conversation text. Hybrid search covers namespaces including rev_user, rev_org, account and conversation, and DevRev's SDK types show a Rev user carries email, full name, phone numbers and a display picture. Search results also return comment bodies, so text written by your customers enters the agent's context.

Can the connector delete or close a DevRev ticket?

It cannot delete one, and it can probably close one. No tool among the 14 carries a delete verb, and DevRev's work-deletion endpoint has no counterpart in the listing. But DevRev's work-update endpoint accepts a stage field, and moving a ticket to a resolved stage is how DevRev closes it, so update_ticket most likely can. Stage changes are reversible.

What do I need before connecting DevRev to Claude?

Admin rights and your organization slug. DevRev's support article states that installing the connector to Claude requires Admin permissions and that the connector must be added to your team before members can connect. The OAuth flow then asks for your slug, which is the string after app.devrev.ai in your workspace URL, so acme for app.devrev.ai/acme.

Are there rate limits on the DevRev MCP server?

Yes, applied per authenticated user across all APIs. DevRev documents a rate-limit window that resets every five minutes, an HTTP 429 response carrying Retry-After when you exceed it, and X-Ratelimit-Limit, X-Ratelimit-Remaining and X-Ratelimit-Reset headers on every response. DevRev states all APIs carry the same weight, with no preference given to any individual API.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put DevRev to work.

Connect DevRev once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio