Mimecast MCP

Mimecast + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

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.

Works with your agent

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

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.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

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

Download 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

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

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, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mimecast/install.ps1 | iex. Then authenticate per the README and run mimecast-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/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

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/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.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, 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 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.

Install for Hermes

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.

Install for OpenClaw

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 the openclaw: frontmatter block.

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

Authenticate

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).

What this skill does

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.

What makes this different

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