Outlook Assistant — MCP server with 22 tools for email, calendar, contacts, and settings via Microsoft Graph API
Outlook Assistant — MCP server with 22 tools for email, calendar, contacts, and settings via Microsoft Graph API. That is what the outlook assistant mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP server for Outlook email, calendar, and contacts — let your AI assistant manage your inbox directly from the conversation.
The server publishes 1 tool. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverThe server ships on npm as @littlebearapps/outlook-assistant, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: OUTLOOK_CLIENT_ID, OUTLOOK_CLIENT_SECRET, OUTLOOK_MAX_EMAILS_PER_SESSION, OUTLOOK_ALLOWED_RECIPIENTS, MS_CLIENT_ID, MS_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Outlook Assistant's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by littlebearapps; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Outlook Assistant's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"outlook": {
"command": "npx",
"args": ["@littlebearapps/outlook-assistant"],
"env": {
"OUTLOOK_CLIENT_ID": "your-application-client-id",
"OUTLOOK_CLIENT_SECRET": "your-client-secret-VALUE"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OUTLOOK_CLIENT_ID | Configuration value read at startup. | Optional |
| OUTLOOK_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| OUTLOOK_MAX_EMAILS_PER_SESSION | Configuration value read at startup. | Optional |
| OUTLOOK_ALLOWED_RECIPIENTS | Configuration value read at startup. | Optional |
| MS_CLIENT_ID | Configuration value read at startup. | Optional |
| MS_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.