MCP server for Mimecast email security: message queue, held messages, domains, and threats.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Mimecast.
{
"MIMECAST_CLIENT_ID": "YOUR_VALUE_HERE",
"MIMECAST_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"MIMECAST_REGION": "us",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-wyre-technology-mimecast-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-io-github-wyre-technology-mimecast-mcp"
],
"env": {
"MIMECAST_CLIENT_ID": "YOUR_VALUE_HERE",
"MIMECAST_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"MIMECAST_REGION": "us",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Mimecast is an MCP server for MCP server for Mimecast email security: message queue, held messages, domains, and threats.. It supports STDIO transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
Mimecast uses STDIO transport. Use the package or command config in Install.
Mimecast inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Mimecast is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/wyre-technology/mimecast-mcp:v1.2.3stdio | oci | Not captured | Env: MIMECAST_CLIENT_ID required Env: MIMECAST_CLIENT_SECRET required secret Env: MIMECAST_REGION Env: MCP_TRANSPORT Env: AUTH_MODE Env: LOG_LEVEL |