Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Explain a held or blocked Mimecast message in one verdict, triage the hold queue, trace phish clicks
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.
MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_ACCOUNT_CODE, MIMECAST_BASE_URL, MIMECAST_TOKEN_URL, MIMECAST_OAUTH_SCOPE, MIMECAST_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, MIMECAST_MCP_READ_ONLY, MIMECAST_NO_LOCAL_DATA, MIMECAST_MCP_HTTP_TOKENValues 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.
MIMECAST_ACCOUNT_CODE envMIMECAST_BASE_URL envMIMECAST_TOKEN_URL envMIMECAST_OAUTH_SCOPE envMIMECAST_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envMIMECAST_MCP_READ_ONLY envMIMECAST_NO_LOCAL_DATA 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 7, 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: MIMECAST_CLIENT_ID, MIMECAST_CLIENT_SECRET, MIMECAST_MCP_HTTP_TOKEN
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.0) reached the registry 2 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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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 Mimecast
API. Not affiliated with, endorsed by, or sponsored by Mimecast Services Limited.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Find a held or blocked Mimecast message, explain why in one verdict, and release it behind a safety check, with hold-queue triage, mail-flow health and phish click tracing built in. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Mimecast skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register mimecast-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host mimecast-mcp over HTTPS with MIMECAST_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token. |
| 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 mimecast-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run mimecast-mcp --transport http with MIMECAST_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host mimecast-mcp over HTTPS with MIMECAST_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
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.
.mcpbDownload Mimecast MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Mimecast 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 mimecast@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Mimecast 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/mimecast/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mimecast/install.ps1 | iex. Then authenticate per the README and runmimecast-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/mimecast/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mimecast/install.sh)
The installer drops both mimecast-cli (the CLI) and mimecast-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
mimecast-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/mimecast/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mimecast/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 mimecast@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 remote Microsoft 365 Copilot / Copilot Studio path. 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/mimecast --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/mimecast --force
Hermes speaks MCP natively, so it can also use the mimecast-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the mimecast skill from https://github.com/servosity/msp-skills/tree/main/skills/mimecast. The skill defines how its required CLI (
mimecast-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.
Mimecast API 2.0 uses OAuth2 client credentials. In the Mimecast Administration Console go to Administration > Services > API and Platform Integrations > Mimecast API 2.0 > Generate Keys, choose the products you need (Email Security Cloud Gateway, Audit Events, Security Events) and a least-privilege role, then set the client ID and secret. API 1.0 access keys do not work.
macOS / Linux:
export MIMECAST_CLIENT_ID=<your-client-id>
export MIMECAST_CLIENT_SECRET= mimecast-cli doctor
Windows (PowerShell):
$env:MIMECAST_CLIENT_ID = "<your-client-id>"
$env:MIMECAST_CLIENT_SECRET = " " mimecast-cli doctor
The CLI exchanges them for a 30-minute bearer token and mints a new one automatically. For data residency, set both MIMECAST_BASE_URL and MIMECAST_TOKEN_URL to your regional gateway (for example https://uk-api.services.mimecast.com and https://uk-api.services.mimecast.com/oauth/token; us-api and de-api work the same way). With Mimecast delegate access, MIMECAST_ACCOUNT_CODE (or --account-code on the workflow commands) selects one customer account. doctor checks config, paths, and API reachability, and verifies the credential with one authenticated read (a 401 reads as rejected, a 404 as a wrong base URL).
| Question your MSP keeps asking | Command |
|---|---|
| Why didn't this message arrive: held, rejected, released or delivered, and by which policy? | mimecast-cli why --from billing@vendor.example --to alice@example.com --since 3d --agent |
| What is in the hold queue, grouped by reason, with a release-risk class per group? | mimecast-cli held triage --since 24h --group-by reason --agent |
| Release this held message for the ticket, only if its hold reason is safe (preview first) | mimecast-cli held release-safe eNo1jr0OgjAYRd-lExample --ticket T-1042 --plan |
| Who clicked this phishing link, and did anyone click through a warning? | mimecast-cli ttp who-clicked https://phish.example/login --since 7d --agent |
| Which users did this phishing sender reach, which clicked, which still have it held? | mimecast-cli threats sender @phish.example --since 3d --agent |
| Every threat, rejection and hold for one mailbox this week | mimecast-cli threats mailbox alice@example.com --since 7d --agent |
| Who released risky held messages this week, and which releases have no ticket? | mimecast-cli held release-audit --since 7d --agent |
| Is mail flowing? One OK/WARN/FAIL verdict | mimecast-cli mailflow --max-queue 200 --stale-after 30m --agent |
These workflow commands call the Mimecast API live, in one run. why reports a stage (held, rejected-at-gateway, released-from-hold, rejected-from-hold, the tracking status, or not-found) with the hold or reject reason, policy, spam score and SPF/DKIM/DMARC checks. held triage returns groups with a risk_class (never-release, likely-junk, policy-review, review) and ready-to-act id_batches. threats mailbox and threats sender report fetch_failures and incomplete_sources, so a short answer is never read as clean. mailflow exits non-zero on FAIL (and on WARN with --fail-on-warn), so an RMM monitor can run it. Every covered Mimecast API 2.0 endpoint is also a typed command (held list, messages search, rejections, ttp url-logs, ...).
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Mimecast integrations, such as the Cortex XSOAR Mimecast pack, expose the API as one action per endpoint, for a playbook or a person to chain. That works for one lookup. It is slow for the questions a service desk actually gets, where one answer needs message tracking, the hold queue, the held release log and the rejection log together.
This connector answers each of those questions in one command. why joins tracking, the hold queue, the release log and the rejection log into one verdict; held triage groups the whole hold queue by reason with a release-risk class; held release-safe checks the hold reason before it releases and records the ticket in a local ledger that held release-audit reads back; threats sender and threats mailbox join the URL Protect, Attachment Protect and Impersonation Protect lo
Only the beginning is shown; read the rest in the repo