MultiMail is published in the official MCP registry. Browse it inside AI Control Tower, click Approve, and your Copilot Studio / Bedrock / Vertex AI agents get governed email.
ServiceNow's AI Gateway shipped its Q1 2026 release with native MCP community registry import inside AI Control Tower. Selecting an MCP server auto-populates URL, auth type, and the exposed tool list — eliminating manual intake. The same release added CIMD (Client Identity Metadata Documents) for automated client registration, so connecting a fleet of Copilot Studio agents to ten approved servers no longer means ten separate registrations.
MultiMail is published in that registry as dev.multimail/mcp-server, authenticated via DNS Ed25519 keys. AI stewards browsing AI Control Tower can find MultiMail, see its 41 tools and OAuth 2.1 setup, and approve it through ServiceNow's normal governance flow. The mailbox-level oversight model (read_only, gated_all, gated_send, monitored, autonomous) layers naturally on top of AI Gateway's server-level lifecycle (In Review → Approved → Active → Deprecated).
Behind the same control plane: AI Gateway's P50/P90/P95 latency observability surfaces MultiMail performance directly in AI Control Tower, and the global pause-and-resume kill switch covers MultiMail traffic alongside every other registered server.
Published as dev.multimail/mcp-server with DNS Ed25519 auth. AI Gateway auto-populates URL, auth type, and the full 41-tool list when you select MultiMail in AI Control Tower — no manual JSON intake.
AI Gateway's In Review → Approved → Active → Deprecated server lifecycle pairs with MultiMail's mailbox-level oversight modes. Promote both in lockstep as agent trust builds.
Client Identity Metadata Documents let a fleet of agents under Copilot Studio, Bedrock, or Vertex AI connect to MultiMail through one approved registration — no per-agent setup.
AI Gateway's P50/P90/P95 latency dashboard surfaces MultiMail performance alongside every other registered server. No separate monitoring stack to wire up.
{
"name": "dev.multimail/mcp-server",
"description": "Email infrastructure for AI agents with graduated oversight, "
"verifiable identity, signed disclosure headers, and 41 MCP tools.",
"version": "0.5.5",
"repository": { "url": "https://github.com/multimail-dev/mcp-server" },
"remotes": [{
"type": "sse",
"url": "https://mcp.multimail.dev/mcp",
"auth": { "type": "oauth2.1" }
}]
}Selecting MultiMail in AI Control Tower's MCP browser pulls this entry. AI Gateway populates URL, auth type, and the 41 exposed tool definitions with one click.
"cm"># AI Gateway issues a CIMD for the calling agent;
"cm""># MultiMail validates the document and binds the agent identity
curl -X POST https://mcp.multimail.dev/oauth/register \
-H "content-type: application/json" \
-d '{
"cimd": "eyJ...",
"client_name": "servicenow-ai-gateway-prod",
"redirect_uris": ["https://your-instance.service-now.com/oauth/callback"]
}'Register once at the AI Gateway level. Every agent under Copilot Studio, Bedrock, or Vertex AI inherits the registration via CIMD — no per-agent setup.
"cm"># Now Assist tool definition referencing the AI Gateway-approved MultiMail server
const incidentEscalationAgent = {
name: "incident-escalation",
instructions: "When an incident reaches Sev 1, send escalation email via MultiMail. "
+ "The mailbox runs in gated_send mode — emails queue for CISO approval.",
tools: ["multimail.send", "multimail.list_mailboxes", "multimail.get_audit_log"]
};
"cm"># AI Control Tower routes the tool call through the registered MCP server
"cm""># and records latency metrics for the dashboard
const result = await aiGateway.invokeAgent(incidentEscalationAgent, {
context: { incident_id: "INC0012345", severity: 1 }
});Now Assist agents reference MultiMail tools by name; AI Gateway handles routing, auth, and observability.
Navigate to AI Gateway → AI Control Tower → MCP Servers in your ServiceNow instance. Select “Browse Registry” to open the community registry view.
Find dev.multimail/mcp-server. AI Gateway auto-populates URL, OAuth 2.1 setup, and the full 41-tool list. Move the server through the In Review → Approved → Active lifecycle per your governance policy.
AI Gateway issues a CIMD for each registered agent client. The first time an agent calls MultiMail, the CIMD is presented and validated — no manual per-agent registration.
In MultiMail, set new mailboxes to gated_send so every outbound email queues for human approval. Promote to monitored or autonomous as the agent demonstrates correct behavior.
AI Gateway's P50/P90/P95 dashboard surfaces MultiMail performance alongside every other registered server. Use the global pause toggle for incident response.
dev.multimail/mcp-server in the official MCP registry at registry.modelcontextprotocol.io with DNS-based authentication via Ed25519 keys. ServiceNow AI Gateway's Q1 2026 release added native registry import, so AI stewards can browse to MultiMail in AI Control Tower, select it, and the URL, OAuth 2.1 auth, and full tool list auto-populate.Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a 38-tool MCP server. Formally verified in Lean 4.