MCP server

Run OutreachBox from Claude, ChatGPT, and Cursor

The OutreachBox MCP server gives the AI assistant you already use 56 tools across research, contacts, campaigns, content, and your inbox, with a scoped API key that decides exactly what it may touch.

Start free and get a key See setup

Published on npm as @outreachbox/mcp · Works with any MCP client

Claude · OutreachBox MCP

run_7f3a · 8/8 steps

Completed

You, in Claude
Find fintech founders in London and start a 3-step sequence
campaigns_prospects_create
Research campaign: fintech founders, London
Created
contacts_bulk
Saving the verified founders it found
20 added
templates_create
3-step sequence in your brand voice
Draft
campaigns_email_create
Sequence attached to your sending inboxes
Ready
Confirm launch
Claude asks before anything is sent
Approved
campaigns_email_launch
First touch goes out at 9:00 local
Live
Reported back
Campaign link and next steps, in the chat
Done

Every step loggedready for next run

Drive it from

Claude
ChatGPT
Cursor
VS Code

Runs on

OpenAI
Anthropic
Google Gemini

What is the OutreachBox MCP server?

It is a Model Context Protocol server that connects AI assistants such as Claude, ChatGPT, Cursor, and VS Code to your OutreachBox workspace. Once connected, the assistant can research prospects, manage contacts, build and launch email campaigns, generate content, and work your inbox through 56 OutreachBox tools, limited to the permissions on your API key.

Setup

Connect in about a minute

Create a key, run one command, restart your client. Pick yours below for the exact command and config.

Step 1
Create a scoped key
In OutreachBox, open Workspace → API Endpoints and choose what the assistant may do. Sending email is off unless you turn it on.
Step 2
Run one command
The CLI writes the config for your client. Prefer doing it by hand? Paste the JSON below instead.
Step 3
Restart and ask
Restart the client, then ask it to plan a campaign, research prospects, or summarise your inbox.

Where it goes: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

Let the CLI write it

npx -y @outreachbox/mcp init --client claude --api-key pb_your_key

Or paste the config

{
  "mcpServers": {
    "outreachbox": {
      "command": "npx",
      "args": [
        "-y",
        "@outreachbox/mcp"
      ],
      "env": {
        "OUTREACHBOX_API_KEY": "pb_your_key"
      }
    }
  }
}

Where it goes: .mcp.json in your project, or ~/.claude.json

Let the CLI write it

npx -y @outreachbox/mcp init --client claude-code --api-key pb_your_key

Or paste the config

{
  "mcpServers": {
    "outreachbox": {
      "command": "npx",
      "args": [
        "-y",
        "@outreachbox/mcp"
      ],
      "env": {
        "OUTREACHBOX_API_KEY": "pb_your_key"
      }
    }
  }
}

Where it goes: .cursor/mcp.json in your project, or ~/.cursor/mcp.json

Let the CLI write it

npx -y @outreachbox/mcp init --client cursor --api-key pb_your_key

Or paste the config

{
  "mcpServers": {
    "outreachbox": {
      "command": "npx",
      "args": [
        "-y",
        "@outreachbox/mcp"
      ],
      "env": {
        "OUTREACHBOX_API_KEY": "pb_your_key"
      }
    }
  }
}

Signed in already? The connect screen in OutreachBox has a one-click "Add to Cursor" button.

Where it goes: .vscode/mcp.json in your project

Let the CLI write it

npx -y @outreachbox/mcp init --client vscode --api-key pb_your_key

Or paste the config

{
  "servers": {
    "outreachbox": {
      "command": "npx",
      "args": [
        "-y",
        "@outreachbox/mcp"
      ],
      "env": {
        "OUTREACHBOX_API_KEY": "pb_your_key"
      }
    }
  }
}

Where it goes: Any client that takes a remote MCP server URL, such as ChatGPT

Server URL

https://api.outreachbox.com/mcp

Config

{
  "mcpServers": {
    "outreachbox": {
      "url": "https://api.outreachbox.com/mcp",
      "headers": {
        "Authorization": "Bearer pb_your_key"
      }
    }
  }
}

Clients that support MCP sign-in can connect with just the URL and approve access on an OutreachBox consent screen, no key to paste.

Already have an account? Open the connect screen to create a key with the config filled in.

Tools

56 tools your assistant can use

Every tool is marked read-only or destructive, so your client knows when to ask before acting.

Research
Prospect, sales, influencer, and topic research campaigns.campaigns_prospects_createcampaigns_sales_createcampaigns_influencer_createresearch_topic_create
Contacts
List, create, update, and bulk-import contacts.contacts_listcontacts_bulkcontacts_update
Email campaigns
Build sequences, then launch, pause, or stop them.campaigns_email_createcampaigns_email_launchcampaigns_email_pause
Inbox
Read replies, check for new mail, and reply in thread.inbox_listinbox_readinbox_reply
Content and design
Articles, monthly content calendars, and brand designs.content_generatecontent_calendar_generatedesigns_generate
Social
See connected accounts and publish posts.social_accounts_listsocial_publish
Deliverability
Sender account health, stats, and verification.email_accounts_statsemail_accounts_verify
Projects and templates
Organise work by project and keep reusable email copy.projects_createtemplates_create
Analytics
Campaign and team performance for reports.analytics_useranalytics_members

Permissions

You decide what it can touch

Each API key carries its own permissions. The server only lists the tools a key is allowed to use, so a read-only key never even sees a tool that sends mail.

Give each assistant its own key, and revoke it any time from API Endpoints.
Agent actions that need sign-off still wait in your Approval Inbox.

Read your workspace
Contacts, campaigns, projects, templates, and analytics
On by default
Read your inbox
Replies and conversation threads
On by default
Create and edit
Add contacts, build campaigns and projects, write templates
On by default
Send email and reply
Launch campaigns and reply from your inbox
Off by default
Run agents and the brain
Execute agents, use Brand Brain memory, handle approvals
Off by default

Skills

Playbooks that teach your assistant OutreachBox

The package bundles Agent Skills: step-by-step playbooks for combining the tools into real work, including when to stop and ask you first.

outreachbox-getting-started
Connecting, scopes, and finding your projects and inboxes
outreachbox-cold-email-campaign
Plan, build, launch, and monitor a sequence end to end
outreachbox-prospect-research
Find and qualify prospects, accounts, and creators
outreachbox-inbox-triage
Classify replies and draft responses
outreachbox-content-engine
Topic research through to posts, calendars, and designs
outreachbox-deliverability
Account health, verification, and warmup checks
outreachbox-analytics-report
Weekly and monthly campaign and team reports

npx -y @outreachbox/mcp skills install --client claude

Download the skills pack

Reference

CLI commands

npx -y @outreachbox/mcp …	What it does
init --client <name> --api-key <key>	Add OutreachBox to a client config (claude, claude-code, cursor, vscode)
skills install --client <name>	Copy the bundled skills into a client
skills list	List the bundled skills
doctor	Check the key, the organization it belongs to, and how many tools it can use

The server reads OUTREACHBOX_API_KEY from its environment. With no command it runs over stdio, which is what MCP clients expect.

FAQ

Frequently asked questions

What is the OutreachBox MCP server?

Which AI assistants can I use?

Claude Desktop, Claude Code, Cursor, and VS Code connect through the @outreachbox/mcp npm package with one command. ChatGPT and other clients that accept a remote server URL connect to https://api.outreachbox.com/mcp.

Do I need an OutreachBox account?

Yes. The server acts on your workspace, so you need an account and an API key. Any account can create keys, and the assistant's requests count toward your plan's API request allowance.

Can the assistant send email without asking me?

Only if you allow it. Sending email and replying is a separate permission that is off by default when you create a key, the server never exposes a tool the key isn't allowed to use, and the bundled skills tell the assistant to confirm before anything is sent.

How is this different from the AI Copilot?

The AI Copilot lives inside OutreachBox. The MCP server brings the same kind of tools to the assistant you already work in, so you can run outreach from Claude, ChatGPT, or your editor without switching apps.

Something is not working. Where do I start?

Run npx -y @outreachbox/mcp doctor. It validates your key, names the organization it is bound to, and reports how many tools the key can use. A key with too few permissions is the most common cause of a missing tool.

Give your assistant a seat on your marketing team

Start free, create a scoped key, and run your first campaign from Claude, ChatGPT, or Cursor today.

Start free

Free plan available
No credit card required
Approval gates you control

Run OutreachBox from Claude, ChatGPT, and Cursor

What is the OutreachBox MCP server?

Connect in about a minute

Create a scoped key

Run one command

Restart and ask

56 tools your assistant can use

Research

Contacts

Email campaigns

Inbox

Content and design

Social

Deliverability

Projects and templates

Analytics

You decide what it can touch

Playbooks that teach your assistant OutreachBox

CLI commands

Frequently asked questions

What is the OutreachBox MCP server?

Which AI assistants can I use?

Do I need an OutreachBox account?

Can the assistant send email without asking me?

How is this different from the AI Copilot?

Something is not working. Where do I start?

Give your assistant a seat on your marketing team