Skip to content

Ticketing

DevRev MCP connector

The DevRev connector brings your customer organizations, customer contacts, team members and groups into Claude, ChatGPT, Cursor or any MCP client, so each person can look them up and keep them current inside their own DevRev access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect DevRev to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect DevRev once

  1. Open Connections, choose Add connection, and pick DevRev.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a DevRev API key. One person generates a token in DevRev and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

devrev
DevRev
Airtable
Asana
Autotask
Basecamp
ClickUp
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect DevRev to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect DevRev to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect DevRev to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect DevRev to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with DevRev through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Find the account behind an inbound request

    Ask for the DevRev customer organization and the contacts attached to it before replying, so you know who is writing and which account they belong to.

  • Customer Success

    Catch the account up after a call

    Update the customer organization and its contacts in DevRev straight after a renewal or check-in call, without opening every record by hand.

  • Sales

    Create the customer record on close

    When a deal closes, create the DevRev customer organization and its first contacts in one ask so support and success see the account from day one.

  • Revenue Operations

    Clean up duplicate contacts and stale accounts

    List DevRev customer organizations and contacts, spot duplicates or records missing a domain or owner, and fix or remove them in bulk.

  • IT

    Review who has a DevRev seat

    List DevRev team members and system users, check who is active, and update details when roles change.

  • Support Operations

    Organize agents into groups

    Create DevRev groups for regions, products or shifts and look up who belongs to each one when routing or planning coverage.

Try asking

  • “Summarize tickets opened this week by rev org.”
  • “Which issues are assigned to me and still open?”
  • “List dev users in the support team.”

See all 101 DevRev tools below

AI tools

DevRev tools for your AI agents

101 tools are ready to call through Elaichi's MCP endpoint the moment you connect DevRev, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting DevRev gets you

6 screens from the product, each doing one job for your DevRev account.

The agent

Ask about tickets, read answers from DevRev.

Plain language questions return live issues, tickets and rev orgs from DevRev.

  • tickets
  • issues
  • dev users
  • rev orgs

Ask Elaichi to work across your apps.

Summarize tickets opened this week by rev org.

Which issues are assigned to me and still open?

List dev users in the support team.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach DevRev here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

101 DevRev tools arrive ready to call.

Tickets, issues, dev users and rev orgs covered with no custom code.

  • List all DevRev me
  • List all DevRev dev users
  • Get single DevRev dev user by ID
  • List all DevRev dev org auth connections
ElaichiTools
Tool Action Description
List all DevRev me List Get information about the authenticated user in DevRev. Returns fields including id, created_by, created_date, display_id, display_name, display_picture, email, full_name, state, experience_start_date, external_identities, job_history, modified_by, modified_date, phone_numbers, and skills.
List all DevRev dev users List List users within your organization in DevRev. Returns fields including id, created_by, created_date, display_id, display_name, email, full_name, state, job_history, modified_by, modified_date, phone_numbers, skills, and external_identities.
Get single DevRev dev user by ID Get Get information about a specific user by id in DevRev. Returns fields including id, created_by, created_date, display_id, display_name, display_picture, email, full_name, state, job_history, modified_by, modified_date, phone_numbers, skills, and external_identities.
List all DevRev dev org auth connections List List all authentication connections for a Dev organization in DevRev. Returns type, display_name, enabled status, id, client_id, and tenant_domain for each connection.
Get single DevRev dev org auth connection by ID Get Get details of a specific authentication connection in DevRev by id. Returns type, display_name, enabled status, id, client_id, and tenant_domain fields.

Toolboxes

Every team gets its own DevRev toolbox.

Support, engineering and success each open a toolbox scoped to their work.

  • Support
  • Engineering
  • Customer success
  • Product
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

DevRev · tickets and conversations

DevRev starter 18 Mar 4, 2026

Engineering toolbox

DevRev · issues and parts

9 Mar 2, 2026

Customer success toolbox

DevRev · rev orgs and accounts

24 Feb 27, 2026

Product toolbox

DevRev · issues and roadmap parts

DevRev starter 6 Feb 19, 2026

Operations toolbox

DevRev · dev users and groups

31 Jan 30, 2026

Leadership toolbox

DevRev · ticket volume and trends

12 Jan 22, 2026

Shared connections

Share a DevRev connection, never a credential.

See who connected each account and which teams and members work through it.

  • Support EMEA
  • Support US
  • Engineering
  • Customer success
ElaichiConnections
Connection Scope Status Access
DE

DevRev (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
DE

DevRev (Support US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
DE

DevRev (Engineering)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
DE

DevRev (Customer success)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
DE

DevRev (Product)

Connected by Clara Nowak

Personal • Active Not shared
DE

DevRev (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every DevRev call is written down.

When, who, what happened, type and resource, in an append only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

DevRev Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

DevRev Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

DevRev Tickets List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, DevRev tickets move.

Six steps fetch and group tickets, draft a digest, await approval, post back.

DevRev digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch tickets

    DevRev

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    DevRev

    Queued

Collections and dashboards

DevRev ticket numbers land without being asked.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

DevRev health

Refreshed 4 minutes ago · every 15 minutes · from the tickets collection

Live

Tickets

1,284 ↓ 12%

Issues

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Tickets created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support US 27%

Engineering 21%

Customer success 18%

FAQ

Frequently asked questions

How do I connect DevRev to Claude?

Connect DevRev in Elaichi first, which means pasting a DevRev API key from your DevRev settings into Elaichi. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and DevRev is available in Claude.

Does DevRev work with ChatGPT and Cursor as well as Claude?

Yes. Once DevRev is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect DevRev once and every client uses that one connection.

What can an AI agent actually do with my DevRev data?

With DevRev connected, an agent can look up customer organizations and the contacts attached to them, create new ones, update details like names and domains, and remove records that should not be there. It can also list your DevRev team members and system users, update their details, and create and look up groups. Because DevRev exposes a lot of actions, short concrete asks such as "find the Acme account and list its contacts" work better than long sentences.

Does connecting DevRev give the AI access to my whole workspace?

No. Every request to DevRev runs inside the access of the person who signed in, so the AI sees only the customer organizations, contacts and team members that person can already see in DevRev. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what DevRev itself allows.

Can my team share one DevRev connection?

Yes. One person connects DevRev in Elaichi and shares the connection with a team, and nobody else ever handles the DevRev API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup or change in DevRev.

Can I stop an agent from deleting or changing things in DevRev?

Yes. Restrictions in Elaichi work per action, so you can allow reading DevRev customer organizations and contacts while blocking creating, updating or deleting them. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a DevRev connection when someone leaves?

Offboarding a person in Elaichi ends their access to DevRev through every client at once. A DevRev connection they shared keeps working for everyone else on the team. If you disconnect DevRev in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

Put DevRev in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.