mcpbeat Sign in

Outreach MCP Server

local only

Outreach runs on your own machine — the client starts it, so there is no endpoint to ping. 56 installs a week from npm. Last commit 2 Nov 2026.

Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings

Installs per day peak 15 · avg 4 · +273% w/w
a month agotoday
56
Installs / week
npm · @mindstone/mcp-server-outreach
14
Stars
2 open issues
2 Nov 2026
Last commit
2 releases in 90 days
FSL-1.1-MIT
License
TypeScript

What the code does

We read the source, 22 h ago · rules 995398eba69f

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a file or shell call replace_workspace_document.document_id → connectors/pandadoc/src/tools/documents.ts:891
          fs.writeFileSync(outFd, pdfBuffer);
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command connectors/office/src/index.ts:403
    const child = spawn(process.execPath, [script], {
  if (isUnder(resolvedAbs, sshDir)) return { hit: true, reason: '~/.ssh/** is sensitive' };
Page loads a third-party script connectors/office/src/addin/taskpane.html:10
  <script src="https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js"></script>
    const entries = fs.readdirSync(workspacePath, { withFileTypes: true });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add mcp-server-outreach -e 'OUTREACH_CLIENT_ID=<OUTREACH_CLIENT_ID>' -e 'OUTREACH_CLIENT_SECRET=<OUTREACH_CLIENT_SECRET>' -- npx -y @mindstone/mcp-server-outreach
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-outreach": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-outreach"
      ],
      "env": {
        "OUTREACH_CLIENT_ID": "<OUTREACH_CLIENT_ID>",
        "OUTREACH_CLIENT_SECRET": "<OUTREACH_CLIENT_SECRET>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server-outreach]
command = "npx"
args = ["-y", "@mindstone/mcp-server-outreach"]
env = { OUTREACH_CLIENT_ID = "<OUTREACH_CLIENT_ID>", OUTREACH_CLIENT_SECRET = "<OUTREACH_CLIENT_SECRET>" }
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server-outreach": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-outreach"
      ],
      "env": {
        "OUTREACH_CLIENT_ID": "<OUTREACH_CLIENT_ID>",
        "OUTREACH_CLIENT_SECRET": "<OUTREACH_CLIENT_SECRET>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp-server-outreach": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-outreach"
      ],
      "env": {
        "OUTREACH_CLIENT_ID": "<OUTREACH_CLIENT_ID>",
        "OUTREACH_CLIENT_SECRET": "<OUTREACH_CLIENT_SECRET>"
      }
    }
  }
}

Put your own values in place of <OUTREACH_CLIENT_ID> (Outreach OAuth client ID (recommended path)), <OUTREACH_CLIENT_SECRET> (Outreach OAuth client secret (recommended path)). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: OUTREACH_ACCESS_TOKEN (Static access token (alternative to OAuth)), OUTREACH_CONFIG_DIR (Custom config directory), OUTREACH_OAUTH_PORT (OAuth callback port (0 = OS-assigned)), OUTREACH_OAUTH_SCOPES (Space-separated OAuth scopes).

Alternatives to Outreach

same job, measured the same way
Apollo.io MCP Server
by inferensys

Apollo.io MCP server for prospecting, enrichment, CRM, sequences, and outreach workflows

local only
Fintalio LinkedIn MCP
by fintalio

LinkedIn outreach MCP server — 19 tools for AI agents to prospect, sequence, and manage contacts.

answering
Reply.io
by reply-io

Manage sequences, contacts, and outreach statistics on Reply.io's sales engagement platform.

answering
Apollo.io
by apolloio

Prospect, enrich leads, and manage outreach sequences with Apollo.io.

answering
Apolloio
by apolloio

Official Apollo.io MCP server for lead enrichment, prospecting, sequences, and analytics.

34 installs/wk local only
Salesforce
by mindstone

Salesforce CRM MCP server: accounts, contacts, opportunities, leads, tasks, and custom objects

79 installs/wk local only
Testera
by sslugic

Free test management over MCP: projects, test cases, plans, runs, environments and tasks.

answering
Niftypm
by niftypm

Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.

answering

Outreach — questions

Answers built from our own checks of this server.

Why is there no uptime for Outreach?
Outreach runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @mindstone/mcp-server-outreach was installed 56 times last week.
How do I connect Outreach?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @mindstone/mcp-server-outreach straight from npm; nothing to host, nothing to sign up for.
How many people use Outreach?
The npm package @mindstone/mcp-server-outreach was installed 56 times in the last week. Week over week that is +273%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Outreach open source?
No, and the distinction matters: its licence is declared as FSL-1.1-MIT. That makes it source-available — you can read the code, but the terms are the author's own, not one of the recognised open-source licences. Read them before you build on it.