Outreach MCP server

Read from the package source without running it. The installed server may list more.

• outreach_add_prospect_to_sequence

  Add a prospect to a sequence. Example: { "prospect_id": "123", "sequence_id": "456" } WORKFLOW: Find the prospect (outreach_search_prospects) and sequence (outreach_list_sequences) first. COMMON MISTAKES: Prospect must not already be active in the same sequence.

• outreach_complete_task

  Mark an Outreach task as completed. Example: { "id": "401" } WORKFLOW: Use outreach_list_tasks with status "incomplete" to find open task IDs.

• outreach_connect_account

  Connect an Outreach account via OAuth. Takes no parameters — call with {}. Initiates OAuth flow — in standalone mode, opens a browser URL for sign-in. In bridge mode, delegates to the host app. WHEN TO USE: - No Outreach account is connected - Authentication errors from other tools - User asks to connect Outreach After connecting, verify with outreach_list_connected_accounts.

• outreach_create_prospectwrite action

  Create a new prospect in Outreach. Example: { "email": "jane@acme.com", "first_name": "Jane", "last_name": "Doe" } REQUIRED: At least email or last_name. COMMON MISTAKES: Don't forget to associate with an account via account_id if known.

• outreach_create_taskwrite action

  Create a task in Outreach, e.g. a follow-up reminder for a prospect. Example: { "note": "Follow up on pricing question", "prospect_id": "123", "due_at": "2026-05-01T17:00:00Z" } WORKFLOW: Use outreach_search_prospects to find the prospect ID first.

• outreach_disconnect_account

  Disconnect an Outreach account. Example: { "username": "user@company.com" } Removes stored credentials. Use when switching accounts or troubleshooting.

• outreach_get_account

  Get full details of an Outreach account (company) by ID. Example: { "id": "789" } Returns account fields, custom fields, and associated prospects count.

• outreach_get_prospect

  Get full details of an Outreach prospect by ID. Example: { "id": "123" } Returns all prospect fields including custom fields, tags, engagement data. RELATED TOOLS: outreach_search_prospects to find IDs first.

• outreach_get_sequence

  Get full details of an Outreach sequence by ID. Example: { "id": "456" } Returns sequence config, steps, and performance metrics.

• outreach_get_sequence_template

  Get a sequence template, including the actual email subject and body. Example: { "id": "901" } A sequence template links a sequence step to its content template. The response includes the sequence template record plus the resolved template's subject and bodyHtml under "template". WORKFLOW: outreach_list_sequence_steps returns the sequenceTemplates IDs for a sequence.

• outreach_list_accounts

  List Outreach accounts (companies). Example: { "name": "Acme" } or { "domain": "acme.com" } Returns company accounts with domain, industry, and owner info.

• outreach_list_calls

  List Outreach calls with direction, outcome, notes, and linked call disposition. Example: { "prospect_id": "123" } or { "user_id": "601" } Returns calls with state, direction (inbound/outbound), outcome (completed/no_answer), answered/completed timestamps, notes, and the callDisposition_id linking to the logged call outcome. Useful for meeting prep and reviewing recent activity.

• outreach_list_connected_accounts

  List connected Outreach accounts. Takes no parameters — call with {}. Call this FIRST before any Outreach operations to verify authentication. Returns auth mode, connection status, and account details.

• outreach_list_mailboxes

  List Outreach mailboxes (connected sender email accounts). Example: {} Returns mailboxes with email address, send/sync status, and owning user. WORKFLOW: Use the returned IDs as mailbox_id when enrolling a prospect with outreach_add_prospect_to_sequence.

• outreach_list_mailings

  List recent mailings (sent emails). Example: { "prospect_id": "123" } or { "limit": 10 } Returns sent emails with subject, status (delivered/bounced/opened), and timestamps.

• outreach_list_sequence_steps

  List the steps of an Outreach sequence. Example: { "sequence_id": "456" } Returns each step's type (auto_email, manual_email, call, task), interval, and order. WORKFLOW: Use outreach_list_sequences to find the sequence ID first, then outreach_get_sequence_template with a step's sequenceTemplates ID to read the email copy.

• outreach_list_sequences

  List Outreach sequences. Example: { "name": "Demo follow-up" } or {} Returns sequences with status, step count, and engagement stats. FILTERS: name (partial match), enabled status.

• outreach_list_tasks

  List Outreach tasks. Example: { "status": "incomplete" } or { "prospect_id": "123" } Returns tasks with status, due date, type, and assigned user.

• outreach_list_users

  List Outreach team members. Example: {} Returns users with name, email, and role information.

• outreach_remove_prospect_from_sequencewrite action

  Pause or finish a prospect's enrollment in a sequence. Example: { "prospect_id": "123", "sequence_id": "456", "action": "pause" } ACTIONS: "pause" (default) stops future sends but can be resumed later; "remove" finishes the enrollment via the sequence state's finish action — the prospect receives no further steps, and re-enrolling restarts the sequence from the top. WORKFLOW: Finds the prospect's

• outreach_search_prospects

  Search Outreach prospects. Example: { "email": "jane@acme.com" } or { "name": "Jane", "limit": 10 } WORKFLOW: Search first, then use outreach_get_prospect for full details. FILTERS: name, email, company, tags. All optional — omit all for recent prospects. PAGINATION: Default 25, max 50. Use page_offset for next page.

• outreach_update_prospectwrite action

  Update an existing prospect. Example: { "id": "123", "title": "VP Sales" } Only provided fields are updated. Use outreach_search_prospects to find the ID.

• Code scan39 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

85/100

higher than 78% of 877 Sales and outbound servers

Tools

22

the typical Sales and outbound server has 10

Tools that change things

18%

typical: 10%. Fewer write tools means less an agent can break

GitHub stars

14

more than 91% of 424 Sales and outbound servers

Downloads a week

17

more than 4% of 180 Sales and outbound servers with a package

Outreach: common questions

Is Outreach MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the Outreach safety report

How do I install Outreach?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Outreach need an API key?

Yes. The registry entry asks for OUTREACH_CLIENT_SECRET, OUTREACH_ACCESS_TOKEN.

Is Outreach maintained?

The last commit was 11 days ago (2026-11-04). The latest release is v0.2.1.

What can I use instead of Outreach?

Servers from other publishers that do the same job: Apollo.io MCP server, Lead Intelligence MCP server and Omentir MCP server. Compare all Outreach alternatives.

How does Outreach compare with other Sales and outbound MCP servers?

safety score 85/100 (higher than 78% of 877 Sales and outbound servers); tools 22 (the typical Sales and outbound server has 10); tools that change things 18% (typical: 10%. Fewer write tools means less an agent can break). Full comparison.