Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Proofpoint TAP threats, VAPs, clickers, and IOCs from your terminal, with a local threat store.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PROOFPOINT_API_SECRET, PROOFPOINT_BASE_URL, PROOFPOINT_SERVICE_PRINCIPALValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PROOFPOINT_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PROOFPOINT_API_SECRET, PROOFPOINT_SERVICE_PRINCIPAL
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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):
| Your AI agent | How to install the Proofpoint skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register proofpoint-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add proofpoint-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add proofpoint-mcp to mcp.json under the servers key, then pick Agent mode. |
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.
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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionproofpoint-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 setPROOFPOINT_CLI_PATHto 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/proofpoint/install.ps1 | iex. Then authenticate per the README and runproofpoint-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
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.
| Question your MSP keeps asking | Command |
|---|---|
| What malicious clicks and messages got through overnight? | proofpoint-cli backfill --since 12h |
| Who is both Very Attacked and a top clicker? | proofpoint-cli risk-overlap --window 30 |
| Give me the full incident brief for a threatId | proofpoint-cli incident "threat-abc123" |
| What indicators should I block from this threat? | proofpoint-cli iocs --threat-id "threat-abc123" --csv |
| Show me every event that touched one user | proofpoint-cli user "jane.doe@example.com" |
| Who are my Very Attacked People this month? | proofpoint-cli people list-vap --window 30 |
| Which permitted clicks and delivered threats still need a response? | proofpoint-cli siem list-issues |
| What threats are inside this campaign? | proofpoint-cli campaign-threats "campaign-xyz789" |
| Decode this urldefense-rewritten link | proofpoint-cli url --urls "https://urldefense.com/v3/..." |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
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.
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
Only the beginning is shown; read the rest in the repo