Postgate AI - Microsoft Exchange MCP Server

Barındırılan çok kullanıcılı MCP sunucusu, Microsoft Exchange için - şirket içi Exchange Server ve hibrit (EWS) dahil: e-posta, takvim, kişiler ve görevler için SSE/Streamable HTTP üzerinden OAuth 2.0/PKCE ile 70'ten fazla araç.

Dokümantasyon

MCP server for Microsoft Exchange Server SE: on-prem (EWS) & hybrid.

Postgate AI exposes Exchange mailboxes as an MCP server, with 90+ tools over Streamable HTTP, OAuth 2.0/PKCE, and delegated per-user permissions. Mailboxes in your own network connect via EWS, which covers Exchange Server Subscription Edition (SE) plus Exchange 2019 and 2016. You can run it fully managed in Germany or self-hosted under license.

Start your free trial

Architecture

Seven things to know about the technology

The MCP standard

The Model Context Protocol is the open standard that lets AI assistants access external systems. Postgate AI exposes Exchange through it, for Claude, ChatGPT, Perplexity, Mistral Vibe, and any other MCP-capable client. We fully support the July 28, 2026 revision, and older clients keep working unchanged.

Transport: Streamable HTTP (July 28, 2026 revision)

The server has exactly one endpoint: /mcp. Since the July 28, 2026 revision of MCP, every request stands on its own, with no session ID and no permanently open stream. TLS encrypts every connection.

Sign-in: OAuth 2.0/PKCE, Entra ID or AD FS

Clients sign in with OAuth 2.0 and PKCE. We verify identity through Microsoft Entra ID, or through your own AD FS if you do not want a cloud sign-in. The server accesses Exchange with the credentials of each user.

Per-user vault

Exchange credentials are stored per user in a vault, encrypted with RSA-4096, either with us in Germany or self-hosted in your own network. Access is delegated and uses the existing Exchange permissions, with no service account and no application impersonation.

Connected via EWS and Microsoft Graph

We connect mailboxes on Exchange Server SE, 2019, and 2016 via EWS, including in hybrid setups. In the fully managed option, we also reach Exchange Online mailboxes via Microsoft Graph. A cloud mailbox is not required.

Several nodes behind one load balancer

When self-hosted on Linux or Kubernetes, several nodes run side by side behind your load balancer. When the number of users grows, you add another node.

90+ tools

Email, calendar, contacts, tasks, folders, attachments (including PDF, DOCX, and XLSX extraction), threads, the global address list, and free/busy times. A self-hosted installation adds semantic search.

Integration

One MCP server, three ways to use it

AI assistants

Use Claude, ChatGPT, Perplexity, and Mistral Vibe on desktop and mobile. Gemini works via Gemini Enterprise or Google Antigravity.

Agent platforms

Microsoft Copilot Studio plugs Postgate AI in as an MCP tool. Your Copilot agent then works with on-premises mailboxes. The same goes for n8n and for any other platform that speaks MCP with OAuth.

Custom agents

Any MCP-capable runtime can use the tools, from a Python script to a full agent platform.

Step-by-step guides: Claude, ChatGPT, Gemini, Perplexity, Mistral Vibe →

FAQ

Frequently asked questions

What is an MCP server for Microsoft Exchange?

It’s a server that makes Exchange mailboxes accessible to AI assistants via the Model Context Protocol (MCP). Emails, calendar, contacts, and tasks become standardized tools that Claude, ChatGPT, Mistral Vibe, or custom agents can call, using each user’s own permissions.

Does the MCP server work with Exchange on-premises?

Yes, that’s the core of it. Postgate AI connects via EWS to Microsoft Exchange Server SE, 2019, and 2016, including hybrid environments. You can run it fully managed or self-hosted under license, and in both cases nothing is installed on clients.

Can I use the MCP server in Copilot Studio or n8n?

Yes, both work. In Microsoft Copilot Studio you add Postgate AI as an MCP tool (Streamable HTTP, OAuth 2.0 with dynamic discovery) and your Copilot agent then reaches on-premises mailboxes. n8n works the same way. In both cases every user works with their own Exchange permissions.

How do users authenticate?

Clients authenticate via OAuth 2.0 with PKCE. Each user’s Exchange credentials are stored encrypted in the per-user vault. Every access is delegated and uses that user’s existing Exchange permissions.

Exchange as an MCP server, ready to try in minutes.

Try the fully managed plan free for 14 days: connect your EWS URL, pair a client, and start using the tools. Contact us for a self-hosted license.