MCP server for the Outlook Meetings Scheduler
Most team communication work still happens through a UI a human drives. Outlook Meetings Scheduler MCP server moves it into the conversation instead. MCP server for the Outlook Meetings Scheduler.
MCP Server for scheduling meetings in Microsoft Outlook using Microsoft Graph API.
The server publishes 6 tools. What each one is for:
Input — name (string)Returns — List of matching people with names and email addressesInputs — - subject (string): Subject of the calendar eventattendees — Array of { email, name (optional), type (optional) }client_credentials — The client_credentials tool exposed by this serverclient_provided_token — The client_provided_token tool exposed by this servernpm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: AUTH_MODE, CLIENT_ID, TENANT_ID, CLIENT_SECRET, USER_EMAIL, ACCESS_TOKEN, TOKEN_EXPIRES_ON, GITHUB_TOKEN. 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.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Outlook Meetings Scheduler's toolset — Input, Returns, Inputs and 3 more — is a fair guide to whether it matches your workflow. It is maintained by anoopt; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Input | name (string) |
| Returns | List of matching people with names and email addresses |
| Inputs | - subject (string): Subject of the calendar event |
| attendees | Array of { email, name (optional), type (optional) } |
| client_credentials | The client_credentials tool exposed by this server. |
| client_provided_token | The client_provided_token tool exposed by this server. |
**Interactive Mode with Custom App:**
```json
{
"mcpServers": {
"outlook-meetings-scheduler": {
"command": "node",
"args": [
"/path/to/outlook-meetings-scheduler-mcp-server/build/index.js"
],
"env": {
"AUTH_MODE": "interactive",
"CLIENT_ID": "<YOUR_CLIENT_ID>",
"TENANT_ID": "<YOUR_TENANT_ID>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTH_MODE | Configuration value read at startup. | Optional |
| CLIENT_ID | Configuration value read at startup. | Optional |
| TENANT_ID | Configuration value read at startup. | Optional |
| CLIENT_SECRET | Credential the server authenticates with. | Yes |
| USER_EMAIL | Configuration value read at startup. | Optional |
| ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| TOKEN_EXPIRES_ON | Credential the server authenticates with. | Yes |
| GITHUB_TOKEN | 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.
MCP server enabling room-based messaging between multiple agents
AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for