Proofpoint MCP

Proofpoint + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Proofpoint

API. Not affiliated with, endorsed by, or sponsored by Proofpoint, Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Proofpoint TAP Threat Insight endpoint plus a local threat store that answers cross-endpoint questions - who is both attacked and clicking, what touched a given user - without re-spending the limited daily API quota. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

Security note (until this connector is reprinted). Do not run HTTP mode

(--transport http), not even on localhost. This build has no password,

listens on every network interface, and predates the browser-rebinding guard,

so a web page you open can reach it. The MCP tools can also make changes with

your credentials. Use the default stdio transport. If you set up a tunnel for

a remote agent, shut it down. A fix is on the way.

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs proofpoint-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion proofpoint-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set PROOFPOINT_CLI_PATH to an existing binary). Details: #331.

Download Proofpoint MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Proofpoint release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install proofpoint@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Proofpoint Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.ps1 | iex. Then authenticate per the README and run proofpoint-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.sh)

The installer drops both proofpoint-cli (the CLI) and proofpoint-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

proofpoint-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update proofpoint@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/proofpoint --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/proofpoint --force

Hermes speaks MCP natively, so it can also use the proofpoint-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the proofpoint skill from https://github.com/servosity/msp-skills/tree/main/skills/proofpoint. The skill defines how its required CLI (proofpoint-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your Proofpoint portal):

PROOFPOINT_API_SECRET=<value> PROOFPOINT_SERVICE_PRINCIPAL=<value> proofpoint-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Proofpoint integrations and MCP servers proxy each question into a live API call. That's fine for one lookup. It dies at scale, when you're asking "who is both Very Attacked and clicking" or "every event that touched this user" - and every one of those calls spends against TAP's hard daily quota of 1,800 SIEM requests and 50 campaign-id lookups.

This skill backfills Proofpoint TAP into a local SQLite mirror with full-text search. Cross-endpoint questions become one local join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like risk-overlap, incident, and user join across SIEM clicks, threat messages, VAP status, clicker status, and forensic evidence - work a stateless API wrapper can't do, and re-queries cost zero additional API calls.

The pain this closes

On r/msp and the Proofpoint community forums the recurring TAP complaint isn't detection quality - it's the API and the dashboard around it. The Threat Insight SIEM endpoints cap you at 1,800 requests per rolling 24 hours and a single call can't span more than a one-hour window, so reconstructing even a day of clicks and messages means looping the API by hand; the campaign-ids endpoint is throttled to just 50 requests a day. And the dashboard answers one screen at a time, so the questions you actually ask during response - who is both attacked and clicking, every event that touched this user, what's inside this campaign - cross endpoints the console never joins. The pattern is the same one teams describe everywhere: export the feeds, re-pull the same windows, rebui