Claude + Outreach: What the Integration Can (and Can't) Do in 2026
Outreach now ships an official MCP server, and it installs straight into Claude as a connector. In 2026 Outreach joined Anthropic’s Model Context Protocol ecosystem and made its MCP Server generally available at https://api.outreach.io/mcp. So the honest answer to “how do I connect Claude to Outreach?” changed this year: for most sellers it’s now a few clicks in Claude’s connector menu, not a self-hosted repo. There’s also the long-standing Outreach REST API and a community CData server if you can’t use the official one.
Here’s each route, when to pick it, and what to use when you want Outreach work that happens without you at the keyboard.
Route 1: The official Outreach MCP server (the one to use)
This is the route Outreach and Anthropic both point you to. In Claude, open Customize > Connectors > +, search “Outreach,” and click Connect. You sign in with your Outreach credentials, clear MFA if your org requires it, and the connector is live in your next conversation. No server to host, no API key to paste.
There are real gates, though. To use it you need an active, licensed Outreach seat and the Amplify add-on with credits on your plan, and an org admin has to switch the server on under Administration > Organization > Org Info > Gen AI. If any of those is missing, the connector won’t authorize.
What Claude can reach through it spans most of the revenue surface: prospect lookup, search, create and delete; account and opportunity lookup, search, create and delete; sequences and prospect progress; meeting transcripts and emails; calendar events and meeting briefings; plus configuration like custom fields and lifecycle stages. Realistic asks:
- “Find prospects at 50–200 person SaaS accounts who replied last week but aren’t in an active sequence.”
- “Summarize where the Acme opportunity stands and pull the last meeting transcript.”
- “Create these six prospects and the account records to go with them.”
One caveat Outreach states plainly: they started their MCP journey with read-only, create, and delete tools only. Update and edit operations aren’t supported yet, so Claude can create a prospect or delete one, but it can’t edit an existing record’s fields through the connector.
Route 2: The Outreach REST API (custom builds and Claude Code)
If you’re wiring Outreach into your own agent, or you need the update/edit operations the MCP server doesn’t yet expose, go straight to the Outreach REST API. It follows the JSON:API 1.0 spec and authenticates with OAuth 2.0 — you register an Outreach app, set redirect URIs, and request scopes (period-separated strings like prospects.write or sequences.all) for exactly the resources and access levels you need.
The API is fuller than the connector: it supports fetching, creating, updating, and deleting prospects; finishing a prospect in a sequence via the sequence state’s finish action; and scheduling one-off mailings and tasks outside sequence automation. In Claude Code or a custom MCP wrapper you can hand Claude those endpoints directly. It’s more setup than the connector, but it’s the honest path when you need write-back or server-to-server access.
Route 3: The CData community MCP server (Claude Desktop, read-only)
If the Amplify add-on is out of reach, there’s a third-party option. CData publishes an open-source Outreach MCP server that connects Claude Desktop to Outreach data through its JDBC driver. It’s read-only — good for letting Claude query and report on Outreach data, not for creating or moving prospects. You run it locally and point Claude Desktop’s config at it, so it’s laptop-bound by design.
The limits that actually matter
- It’s gated, not free. The official server needs a licensed seat plus the Amplify add-on with credits and an admin toggle. That’s a real barrier for smaller teams.
- No update/edit through the connector. Read, create, delete only. Editing an existing record still means the API or the Outreach UI.
- No event triggers. Nothing fires when a prospect replies or when a sequence finishes. Cowork’s scheduled tasks can run Outreach work unattended on a clock you set, but the clock is the only trigger on offer — a reply that lands at 9:05 waits for the 5pm run.
- Laptop-bound on the local path. Claude Desktop and CData’s server only work while your machine is on. The official remote connector doesn’t have that problem, but it still waits for you or for the schedule.
- claude.ai on the web reaches the official connector fine, but it can’t touch a local Claude Desktop / CData setup.
The Outreach MCP server is excellent for asking questions and doing one-off work — “what’s the state of my pipeline, add these prospects” — and fine for a standing morning report. It’s not built for responding to a prospect the moment they engage.
If you want Outreach work that runs on its own: Carly
Claude acts when you ask or when the clock says so. Carly is an AI executive assistant that acts when Outreach says so — on the reply, the sequence completion, the booked meeting, as they happen.
- When a prospect replies in Outreach, Carly logs the reply, drafts a response for your review, and books the meeting on your calendar.
- When a sequence finishes with no reply, Carly flags the prospect and starts a follow-up task so nobody goes cold.
- Every morning, Carly pulls the prospects that engaged overnight and sends you a ranked list before you open your laptop.
No-code setup — there’s nothing to host. Carly interviews you about the workflow in plain English and builds it. It actually sends — replies and follow-ups go out through Gmail and Outlook, not just drafted in a window. It connects to anything — Carly reaches Outreach through your own Outreach API access (connect it on the integrations page), one of 200+ native integrations plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude + Outreach | Carly | |
|---|---|---|
| Read / search Outreach | Yes (official MCP) | Yes |
| Create prospects & accounts | Yes | Yes |
| Update / edit records | API only, not connector | Yes |
| Acts on triggers (reply, sequence end) | No | Yes |
| Runs on a schedule | Yes (fixed clock, via Cowork) | Yes |
| Works while your laptop is closed | Official connector yes; local CData server no | Yes |
| Sends email (Gmail + Outlook) | No | Yes |
| Pricing | Pro $20 / Max $100–$200 (+ Outreach Amplify add-on) | AI agents from $35/mo |
Claude is the best way to ask Outreach questions and do one-off work; Carly is the way to make the outbound motion react in the moment.
Frequently Asked Questions
Does Claude work with Outreach?
Yes. In 2026 Outreach shipped an official MCP server that installs as a Claude connector — open Customize > Connectors in Claude, search “Outreach,” and connect. You need a licensed seat and the Amplify add-on enabled.
Is there an official Outreach MCP server in 2026?
Yes. Outreach’s MCP server is generally available at https://api.outreach.io/mcp and Outreach has joined Anthropic’s MCP ecosystem. It exposes read, create, and delete tools across prospects, accounts, opportunities, sequences, and meetings — but not update/edit yet.
Can claude.ai on the web access Outreach?
Yes, through the official remote connector once your admin enables the MCP server and you authorize it. It can’t reach a local Claude Desktop or CData server, which only run while your own machine is on.
Can Claude reply to prospects and book meetings automatically?
Not on its own — Claude has no event triggers, so nothing starts when a prospect replies; the most you get is a scheduled sweep that finds the reply later. Carly handles that unattended: it logs the reply, drafts a response through Gmail or Outlook, and books the meeting.
More: Claude connectors, explained · Claude + Apollo · Claude + Salesforce · Best AI CRM tools · Can Claude send emails?
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
