EWS Meeting MCP

What this does

EWS Meeting MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

EWS_ENDPOINT
EWS_EMAIL
EWS_USERNAME
EWS_PASSWORD
EWS_PASSWORD_KEYCHAIN_SERVICE
EWS_PASSWORD_KEYCHAIN_ACCOUNT
EWS_AUTH_TYPE
EWS_TIMEZONE

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install EWS Meeting MCP?

Run the Claude Code command in the install section to add EWS Meeting MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with EWS Meeting MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to EWS Meeting MCP as well.

Does EWS Meeting MCP need an API key?

Yes. Before it can run, set these environment variables: EWS_ENDPOINT, EWS_EMAIL, EWS_USERNAME, EWS_PASSWORD, EWS_PASSWORD_KEYCHAIN_SERVICE, EWS_PASSWORD_KEYCHAIN_ACCOUNT, EWS_AUTH_TYPE, EWS_TIMEZONE. They go in the env block of your MCP config.