Skip to content

Outreach MCP connector

The Outreach connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read and update the prospects, accounts, calls, mailings, and events in Outreach, with each person signed in as themselves and every action logged.

  • How it connects. Connects over OAuth. 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 Outreach to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Outreach once

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

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

  3. Supply your own Outreach app, then approve. Outreach needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

Add connection

Choose a connector.

outreach
Outreach
Autobound
Gong
Interseller
Lemlist
Salesloft
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.

Outreach MCP connector for 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.

Outreach MCP connector for 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.

Outreach MCP connector for 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 Outreach 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 Outreach through Elaichi

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

  • Sales

    Catch a prospect up after a call

    Log the call in Outreach and update the prospect's title, stage, or notes while the conversation is still fresh, without leaving the tool you are already working in.

  • Sales Development

    Find prospects who went quiet

    Ask for prospects at a target account who have had no reply in two weeks, then queue a follow-up mailing for each one.

  • Sales Development

    Add new prospects from a list

    Paste a list of names, companies, and emails and have the prospects created in Outreach and attached to the right accounts.

  • Sales Operations

    Clean up duplicate or stale accounts

    Pull every account with a given domain, compare what is there, and update or remove the records that no longer belong.

  • Sales Leadership

    Review this week's calls and replies

    Get a plain-language rundown of calls logged and mailing events, such as opens and replies, across the team before the pipeline meeting.

  • Revenue Operations

    Keep Outreach users and seats current

    List who has an Outreach user, add a seat for a new hire, and update or remove users when roles change.

Try asking

  • “List Outreach prospects added to my sequences this week.”
  • “Which Outreach accounts have no prospects assigned yet?”
  • “Summarize sequence activity for my Outreach users this month.”

See all 257 Outreach tools below

Compare

Elaichi vs Zapier MCP vs Composio for Outreach

All three can connect Outreach to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Outreach, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Outreach tools Allow or restrict single Outreach tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Outreach call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Outreach tools for your AI agents

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

See it in Elaichi

What connecting Outreach gets you

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

The agent

Ask about prospects, read the answer.

Plain language questions answered from live Outreach prospects, accounts and sequences.

  • prospects
  • accounts
  • users
  • sequences

Ask Elaichi to work across your apps.

List Outreach prospects added to my sequences this week.

Which Outreach accounts have no prospects assigned yet?

Summarize sequence activity for my Outreach users this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Outreach endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, with no SDK or shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

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

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

257 Outreach tools ready to call.

Users, accounts, prospects and sequences covered without writing custom code.

  • List all Outreach users
  • Get single Outreach user by ID
  • Delete a Outreach user by ID
  • Update a Outreach user by ID
ElaichiTools
Tool Action Description
List all Outreach users List List Outreach users. Returns each user record with type, id, attributes (email, firstName, lastName, locked, createdAt, updatedAt), and relationships.
Get single Outreach user by ID Get Get a single Outreach user by id. Returns: attributes, id, relationships, type. Required: id.
Delete a Outreach user by ID Delete Lock an Outreach user account by id (soft delete via the locked attribute). Returns: attributes, id, relationships, type. Required: id.
Update a Outreach user by ID Update Update an existing Outreach user by id. Returns: attributes, id, relationships, type. Required: id, data.type, data.id.
Create a Outreach user Create Create a new Outreach user, sending an email invitation by default (suppress via meta.sendInvite=false). Returns: attributes, id, relationships, type. Required: data.type, data.attributes.email.

Toolboxes

Every team gets its own Outreach toolbox.

Curate separate toolboxes so sales, marketing and ops see different Outreach tools.

  • Sales
  • Sales development
  • Marketing
  • Revenue operations
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Outreach · prospects and accounts

Outreach starter 18 Mar 4, 2026

Sales development toolbox

Outreach · sequences and mailings

— 9 Mar 2, 2026

Marketing toolbox

Outreach · prospect lists and tags

— 24 Feb 27, 2026

Revenue operations toolbox

Outreach · users and account hygiene

Outreach starter 6 Feb 19, 2026

Customer success toolbox

Outreach · account owners and contacts

— 31 Jan 30, 2026

Enablement toolbox

Outreach · sequence templates and snippets

— 12 Jan 22, 2026

Shared connections

Share an Outreach account, never the credential.

See who connected each Outreach account and which teams and members use it.

  • Sales EMEA
  • Sales AMER
  • Outbound SDR
  • Marketing
ElaichiConnections
Connection Scope Status Access
OU

Outreach (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
OU

Outreach (Sales AMER)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
OU

Outreach (Outbound SDR)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
OU

Outreach (Marketing)

Connected by Tyler Reed

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

Outreach (Revenue operations)

Connected by Ryan Hayes

Personal • Active Not shared
OU

Outreach (Customer success)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Outreach call is on the record.

When, who, what happened, type and resource for each prospect and account change.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Outreach Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Outreach Prospects Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Outreach Prospects 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, Outreach work gets done.

Fetch prospects, group them, draft a digest, approve it, post back to Outreach.

Outreach digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch prospects

    Outreach

    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

    Outreach

    Queued

Collections and dashboards

Outreach numbers arrive before anyone asks.

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

Outreach health

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

Live

Prospects

1,284 ↓ 12%

Accounts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Prospects created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales AMER 27%

Outbound SDR 21%

Marketing 18%

FAQ

Frequently asked questions

How do I connect Outreach to Claude?

First, connect Outreach in Elaichi. Outreach connects over OAuth, but it asks each company to register its own OAuth application inside Outreach, so someone with admin rights brings a client ID and secret once and then signs in with their normal Outreach login. Second, in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Nobody else on the team ever handles the client ID or secret again.

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

Yes. Once Outreach is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Outreach once and use it from whichever client you are in.

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

An agent can look up prospects, accounts, and users in Outreach, create new prospects and accounts, and update them after a call. It can log calls, send mailings, and read mailing events such as opens and replies to tell you who has engaged. Because Outreach exposes a lot of actions, short concrete asks like "log a call with Dana at Acme" work better than long paragraphs.

Does connecting Outreach give the AI my whole Outreach workspace?

No. Every request runs as the person who signed in, so an agent sees only the Outreach prospects, accounts, and mailings that person can already see. Elaichi can narrow that further by team or by action, and it can never grant more access to Outreach than the person already has.

Can my team share one Outreach connection?

Yes. One admin connects Outreach in Elaichi and shares the connection with a team, and nobody else has to touch the client ID or secret. Each teammate still signs in as themselves, so every call and mailing created through the shared Outreach connection is logged under their own name.

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

Yes. In Elaichi you can block individual actions for Outreach, such as deleting prospects, deleting accounts, or removing users, while leaving reads and updates available. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can trigger it.

What happens to an Outreach connection when someone leaves?

When you offboard someone in Elaichi, their access to Outreach through Elaichi ends at once. If they had shared an Outreach connection with a team, it keeps working for everyone else. Disconnecting Outreach once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Does the Outreach MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Outreach is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Outreach?

Yes. Both let Claude, ChatGPT or Cursor use Outreach. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Outreach call.

How is Elaichi different from Composio for Outreach?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Outreach: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Outreach in front of your team

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

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.