Mimecast MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Mimecast MCP Server
An MCP server for the Mimecast API 2.0, the email security gateway MSPs run in front of their clients' mailboxes. It lets an AI agent track where an email went, review and release held messages, read Targeted Threat Protection logs (URL clicks, attachment sandboxing, impersonation), list threat remediation incidents, read the audit log of administrative changes and check the inbound / outbound mail queues.
Transport: MCP Streamable HTTP at
POST /mcp, health probe atGET /healthStateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first
tools/listPython 3.12, uv, FastMCP, httpx
License: Apache-2.0, Copyright 2026 MSPbots.ai
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: Check Point Avanan MCP Server
Authentication headers
Header | Required | Type | Default | Allowed values | Description | Example |
| Yes | string | none | - | API 2.0 application client id |
|
| Yes | string | none | - | API 2.0 application client secret |
|
| No | string | global | a region code ( | API gateway to use |
|
Where to get them: in the Mimecast Administration Console go to Administration > Services > API and Platform Integrations > Available Integrations, and choose Generate Keys on the Mimecast API 2.0 tile. Give the application a role with only the permissions the tools below need.
How they are used: the server exchanges the client id and secret for an access token
(POST https://api.services.mimecast.com/oauth/token, client credentials grant, 30 minute lifetime,
cached in memory per credential set and renewed on expiry) and sends it as Authorization: Bearer.
Region codes all use the global gateway, which serves every account and fails over between regions;
us-api, uk-api and de-api pin traffic to that regional gateway (data residency, no failover).
A request to /mcp without the client id or secret gets HTTP 401. An unknown region does not block
the request (tools/list still works); every tool call then returns an invalid_argument error naming
the accepted values, and nothing is sent to any host.
Tools
All tools return a JSON string. Lists take page_size (max 100) and page_token, and return
{count, has_more, next_page_token}. Dates are ISO 8601 with a zone (2026-03-01T00:00:00Z or
+0000).
Area | Tool | Mimecast permission |
Overview |
| - |
Messages |
| Gateway / Tracking / Read |
| Gateway / Tracking / Read | |
| Account / Dashboard / Read | |
| Account / Monitoring / Held / Edit | |
| - | |
Threats |
| Monitoring / URL, Attachment or Impersonation Protection / Read |
| Services / Threat Remediation / Read | |
| Account / Logs / Read | |
Queues |
| Account / Dashboard / Read |
Policies |
| Gateway / Policies / Read |
| Gateway / Policies / Read | |
| Gateway / Managed Senders / Edit |
Bold parameters are required. mimecast_release_message and mimecast_manage_sender return
{"done": false, ...} until called again with confirm: true after the user approved the change.
Errors come back as a JSON envelope instead of an exception:
{"error": {"code": "unauthorized", "message": "Mimecast rejected the client id / client secret (...)", "retryable": false}}code is one of not_configured, unauthorized, not_found, invalid_argument,
rate_limited, upstream_error. Mimecast reports per-item failures inside an HTTP 200 response
(fail); those become the same envelope. Reads are retried with backoff on 429 (honouring
X-RateLimit-Reset), 5xx and network errors; a release only on 429, so it never runs twice. An
expired or revoked token is renewed once automatically.
Run locally
uv sync
uv run python -m mimecast_mcp # listens on 0.0.0.0:8080or with Docker:
docker build --platform linux/amd64 -t mimecast-mcp:dev .
docker run --rm -p 8080:8080 mimecast-mcp:devConfiguration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0),
MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read
from the environment.
Testing example
# list tools
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Mimecast-Client-ID: your-client-id" \
-H "X-Mimecast-Client-Secret: your-client-secret" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
# where did mail from a sender go today
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Mimecast-Client-ID: your-client-id" \
-H "X-Mimecast-Client-Secret: your-client-secret" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"mimecast_find_message","arguments":{"sender_address":"billing@example.org"}}}'Unit tests (no network access needed):
uv run pytestDelivery notes
Tool names (10 earlier + 1 new). The ten earlier names and their required parameters are unchanged. New:
mimecast_list_held_messages, because releasing needs the held-message id, which only that list returns (message tracking ids are different).Policies (3 new tools, PRD-21236).
mimecast_list_policies/mimecast_get_policycoverblockedsendersandantispoofing-bypasspolicy types via the same/api/policy/{type}/get-policyendpoint every tool in this repo already calls ({"data": [{}]}to list,{"data": [{"id": ...}]}to get one).address-alterationis a valid Mimecast policy type but its endpoint was not independently confirmed from a quotable source, so it is not included — add it once confirmed against the live OpenAPI spec or a sandbox account. Full policy create/edit/delete is out of scope: it changes mail flow for the whole account, a materially larger blast radius than anything else this server does;mimecast_manage_senderinstead exposes the lowest-blast-radius write Mimecast has for this purpose (permit/block one sender for one mailbox), gated byconfirm: trueexactly likemimecast_release_message. Exact field names beyond what is documented above are a pass-through of whatever Mimecast returns, not independently verified against a live account.API source. The official Mimecast API 2.0 OpenAPI documents published on developer.services.mimecast.com (Email Security Cloud Gateway, Security Events, Audit Events, Threat Management) and its API Overview (token, pagination, regional gateways, rate limits).
Routes fixed. Earlier versions called endpoints that do not exist in the API:
/api/gateway/release-message(now/api/gateway/hold-release),/api/gateway/get-queue-stats(now/api/email/get-email-queues, which needs a time window: default the last hour) and/api/ttp/remediation/get-incidents(now/api/ttp/remediation/find-incidents, default the last 30 days).Results fixed. Message tracking and remediation results are nested in the response (
trackedEmails,incidents); earlier versions returned the wrapper, so the count was always 1.Message tracking filters now use the API's fields: sender / recipient go to the advanced tracking options,
valuesearches the subject (or is used as the internet message id when it looks like<id@host>), andstatususes the tracking states. The earlier status names map to them: delivered = delivery + archived, blocked = rejected, failed = bounced, queued = delivery.mimecast_hold_messageis not available: the API has no call that puts a message on hold (messages are held by policy). The tool stays for compatibility and returnsinvalid_argumentpointing to the held-message list and to threat remediation in the console.Removed: the
statusfilter ofmimecast_get_threat_incidents(the API has no such field, so it never filtered); it is replaced bytype(notify_only, automatic, manual, restore) and a search on code / file hash / reason. The incidenttypefilter is sent as{"fieldName": "type", "value": ...}, the API's usual filter form; the reference's wording for this endpoint is ambiguous and it has not been checked against a live account.Release needs confirmation (
confirm: true): releasing delivers mail that a policy held, possibly malicious.Not included: the message "card" UI resource of older versions (an MCP Apps HTML view); the tools return the same data as JSON. Credentials from environment variables are not supported: they would be shared by every caller.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Email safety MCP server. Detects phishing, prompt injection, CEO fraud for AI agents.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email, calendar and contacts for AI agents: Gmail, Microsoft 365 and IMAP accounts behind one API.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for Mimecast Email Security — message tracking, threat intelligence, and email queue management. Enables AI assistants to investigate and manage email security events.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to triage security events, search scanned emails and files, quarantine or restore messages, and manage allow/block exception rules through the Harmony Email & Collaboration API. Runs as a stateless, multi-tenant streamable HTTP endpoint where credentials are supplied per request as headers and never stored.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and read tickets and their conversations, contacts, companies, agents, groups, knowledge base articles, SLA policies, business hours and canned responses, and, on explicit request, create and update records, reply to tickets, add notes, and perform confirmed deletes, merges or conversions. It is stateless and multi-tenant, taking per-request credentials via HTTP headers so every action is performed as the designated agent.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search an email security gateway's quarantine, inspect held messages, read sender allow and block lists and mail flow statistics. On explicit request it can also release or delete quarantined messages and add or remove list entries.Apache 2.0