EWS Meeting MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 76 installs a week from npm. Last commit 18 Sep 2026.
Safely schedule Outlook meetings on on-prem Exchange EWS with preview-confirmed writes.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawnSync(python, pythonArgs, {
result = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ews-meeting-mcp -e 'EWS_ENDPOINT=<EWS_ENDPOINT>' -e 'EWS_EMAIL=<EWS_EMAIL>' -e 'EWS_USERNAME=<EWS_USERNAME>' -- npx -y ews-meeting-mcp{
"mcpServers": {
"ews-meeting-mcp": {
"command": "npx",
"args": [
"-y",
"ews-meeting-mcp"
],
"env": {
"EWS_EMAIL": "<EWS_EMAIL>",
"EWS_ENDPOINT": "<EWS_ENDPOINT>",
"EWS_USERNAME": "<EWS_USERNAME>"
}
}
}
}[mcp_servers.ews-meeting-mcp]
command = "npx"
args = ["-y", "ews-meeting-mcp"]
env = { EWS_ENDPOINT = "<EWS_ENDPOINT>", EWS_EMAIL = "<EWS_EMAIL>", EWS_USERNAME = "<EWS_USERNAME>" }{
"mcpServers": {
"ews-meeting-mcp": {
"command": "npx",
"args": [
"-y",
"ews-meeting-mcp"
],
"env": {
"EWS_EMAIL": "<EWS_EMAIL>",
"EWS_ENDPOINT": "<EWS_ENDPOINT>",
"EWS_USERNAME": "<EWS_USERNAME>"
}
}
}
}{
"servers": {
"ews-meeting-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ews-meeting-mcp"
],
"env": {
"EWS_EMAIL": "<EWS_EMAIL>",
"EWS_ENDPOINT": "<EWS_ENDPOINT>",
"EWS_USERNAME": "<EWS_USERNAME>"
}
}
}
}Put your own values in place of
<EWS_ENDPOINT> (Exchange EWS endpoint, for example https://mail.company.com/EWS/Exchange.asmx), <EWS_EMAIL> (Mailbox email address used as the meeting organizer), <EWS_USERNAME> (Exchange login username, often DOMAIN\username for NTLM).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
EWS_PASSWORD (Exchange password. Prefer macOS Keychain variables when possible), EWS_PASSWORD_KEYCHAIN_SERVICE (Optional macOS Keychain service name for reading the password locally), EWS_PASSWORD_KEYCHAIN_ACCOUNT (Optional macOS Keychain account. Defaults to EWS_USERNAME when omitted), EWS_AUTH_TYPE (Exchange auth type. Usually NTLM for on-prem Exchange), EWS_TIMEZONE (IANA timezone for calendar operations).
Alternatives to EWS Meeting MCP
same job, measured the same wayOutlook / Microsoft 365 for Claude — triage mail, reply, answer invites and book meetings, confirmed
Manage Chili Piper scheduling links, meetings, routing rules, and teams. Admin only. Experimental.
Group meeting scheduler — rank times everyone's free across Google & Outlook, book Meet/Teams.
A MCP server that works with Outlook Calendar to manage event listing, reading, and updates.
Connect inboxes to your AI, with built-in progress and optional owner-confirmed outgoing email.
Planning Center MCP server: send scheduling emails, list unconfirmed volunteers.
MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes.
Safe email for AI agents: a mailbox with inbound scanning, outbound checks and human review.
EWS Meeting MCP — questions
Answers built from our own checks of this server.