simply-outlook-mcp
Enables AI assistants to manage Outlook calendars and emails through the Microsoft Graph API, supporting calendar events, email operations, and selective tool control.
README
Simply Outlook MCP Server
A Model Context Protocol (MCP) server that enables AI assistants to interact with Microsoft Outlook calendars and emails through the Microsoft Graph API.
๐ Features
๐ Calendar Management
- Get Calendar Events - Retrieve calendar events within specified date ranges
- Create Calendar Events - Create personal calendar events
- Create Events with Invites - Create calendar events and send invitations to attendees
- Update Calendar Events - Modify existing calendar events (subject, time, location, etc.)
๐ง Email Operations
- Get Messages - Fetch recent Outlook messages with date filtering
- Get Message Content - Retrieve full content of specific messages by ID
- Search Messages - Search emails by keywords (sender, subject, content)
- Send Messages - Send new emails to specified recipients
- Reply to Messages - Reply to existing email messages
- Pagination Support - Handle large result sets with skip/limit parameters
โ๏ธ Configuration
- Selective Tool Control - Enable/disable individual tools via environment variables
- Environment Configuration - Flexible setup via environment variables
- TypeScript Support - Full type definitions included
๐ Prerequisites
- Node.js 20.19.0 or higher
- Azure AD Application:
Calendars.ReadWrite- Read and write calendar eventsMail.Read- Read email messagesMail.Send- Send email messagesUser.Read- Read user profile information
๐ ๏ธ Installation
Using npx (Recommended)
No installation required! Simply use npx to run the latest version:
Global Installation (Optional)
If you prefer to install globally:
npm install -g simply-outlook-mcp
From Source
For development or customization:
npm install
npm run build
๐ง Setup
[!NOTE] Security Best Practice: We recommend creating your own Azure AD application rather than using a client ID from an unknown 3rd party or untrusted publisher.
This MCP server runs locally. The code that uses the Microsoft Graph access tokens stays on your machine. The Azure AD / Entra "client ID" you supply only tells the directory which app registration to issue tokens for. If you reuse an arbitrary or thirdโparty client ID, you do not automatically leak your tokens to that party, but you are accepting several avoidable risks tied to the app registration that they control.
What a third party CAN change later if you use their client ID:
- Display name / branding you see during future consent prompts (could lower your guard)
- The set of requested delegated scopes (you may click "Accept" again out of habit)
- Publisher domain / verification state (influences user trust signals)
- Authentication settings (enabling flows they host to phish you for tokens)
1. Azure AD Application Registration
- Go to the Azure Portal
- Navigate to Microsoft Entra ID > Manage > App registrations
- Click New registration
- Configure:
- Name: (Any name you like, will show up in the consent dialog)
- Supported account types:
Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox) - Redirect URI: Leave blank
- After creation, in the application resource view, note down client ID in the Overview page:
- Application (client) ID
- In the application resource view, go to Manage > Authentication page:
- Toggle
Enable the following mobile and desktop flowstoYes
- Toggle
[!NOTE] The scopes currently requested by this MCP are designed to work with personal Microsoft account (MSA).
2. Authentication Setup
npx simply-outlook-mcp --auth --client_id YOUR_CLIENT_ID
This will open a browser for device authentication. Sign in with your Microsoft account that has access to the Outlook data you want to manage.
๐ Usage
Using with MCP Clients
The server implements the Model Context Protocol and can be used with any MCP-compatible AI assistant.
Example configuration for Claude Desktop:
{
"mcpServers": {
"simply-outlook-mcp": {
"command": "npx",
"args": [
"-y",
"simply-outlook-mcp"
],
"env": {
"SIMPLY_OUTLOOK_MCP_CLIENT_ID": "your-client-id",
}
}
}
}
VS Code
{
"servers": {
"simply-outlook-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"simply-outlook-mcp"
],
"env": {
"SIMPLY_OUTLOOK_MCP_CLIENT_ID": "your-client-id"
}
}
}
}
Environment Variables
The following environment variables can be used to configure the MCP server:
Required Variables
| Variable | Description | Example |
|---|---|---|
SIMPLY_OUTLOOK_MCP_CLIENT_ID |
Azure AD Application (client) ID | 12345678-1234-1234-1234-123456789012 |
Optional Variables
| Variable | Description | Default | Example |
|---|---|---|---|
SIMPLY_OUTLOOK_MCP_TENANT_ID |
Ignore this, for advance usage if you create single tenant or MSA only app | common |
|
SIMPLY_OUTLOOK_MCP_DISABLED_TOOLS |
Comma-separated list of tools to disable | None | get-calendar-events,send-outlook-message |
Tool Names for Disabling
You can disable specific tools by adding their names to the SIMPLY_OUTLOOK_MCP_DISABLED_TOOLS environment variable:
Calendar Tools:
get-calendar-events- Retrieve calendar eventscreate-calendar-event- Create personal calendar eventscreate-calendar-event-with-invite- Create events with invitationsupdate-calendar-event- Modify existing calendar events
Email Tools:
get-outlook-messages- Fetch recent messagesget-outlook-message-content- Get full message contentsearch-outlook-messages- Search emails by keywordssend-outlook-message- Send new emailsreply-outlook-message- Reply to existing emails
Example Configuration
{
"mcpServers": {
"outlook": {
"command": "npx",
"args": [
"-y",
"simply-outlook-mcp"
],
"env": {
"SIMPLY_OUTLOOK_MCP_CLIENT_ID": "12345678-1234-1234-1234-123456789012",
"SIMPLY_OUTLOOK_MCP_DISABLED_TOOLS": "create-calendar-event-with-invite,update-calendar-event,send-outlook-message,reply-outlook-message"
}
}
}
}
[!TIP] Disabling Tools: You can disable tools you don't need for security or functionality reasons. For example, disable email sending tools (
send-outlook-message,reply-outlook-message) if you only want read-only email access.
License
MIT License - see LICENSE file for details.
Support
- GitHub Issues: Report bugs or request features
- Repository: https://github.com/hmmroger/simply-outlook-mcp
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.