DevRev

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.

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.

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.

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.

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.

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.

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.

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.