outlook-meetings-scheduler

The Outlook Meetings Scheduler MCP Server exposes a set of Graph-based calendar utilities that you can invoke through MCP clients. It includes tools to locate attendees by name, create calendar events, create events with attendees, fetch event details, list events, delete events, and update events or their attendee lists. Use find-person to resolve emails from names, then pass those addresses into create-event-with-attendees or update-event-attendees as needed. The server supports three authentication modes: interactive (delegated), client credentials (app-only), and client-provided token. If you don’t specify AUTH_MODE, the server will attempt to auto-detect based on the presence of credentials in your environment. In interactive mode, you’ll be prompted to log in; in app-only mode, the server authenticates as an app; in client-provided token mode, you supply an access token. This makes it suitable for local development, automated workflows, or client-integrated usage with Planner-like tooling. The tools are designed to work with Microsoft Graph, returning event details, URLs, IDs, and attendee lists, so you can thread calendar actions into broader MCP-based workflows (for example, linking a GitHub issue to a calendar reminder).

Prerequisites:

• Node.js and npm installed on your machine
• Access to a Microsoft 365 tenant and an Azure AD app registration if using app-only or delegated modes

Steps:

1. Clone the MCP server repository:

git clone https://github.com/anoopt/outlook-meetings-scheduler-mcp-server.git
cd outlook-meetings-scheduler-mcp-server

2. Install dependencies:

npm install

3. Build the project (if a build step exists in your repo):

npm run build

4. Create or update the MCP configuration file (example shown below) and point the server to its path. If you’re using VS Code, you can place this JSON in .vscode/mcp.json or User Settings JSON as appropriate.

{
  "mcpServers": {
    "outlook-meetings-scheduler": {
      "command": "node",
      "args": ["path/to/server.js"]
    }
  },
  "env": {
    "AUTH_MODE": "interactive|client_credentials|client_provided_token",
    "CLIENT_ID": "<Azure AD Client ID>",
    "TENANT_ID": "<Tenant ID>",
    "CLIENT_SECRET": "<Client Secret for app-only mode>",
    "ACCESS_TOKEN": "<Pre-acquired access token for token-based mode>"
  }
}

5. Run the MCP server (adjust the path to server.js as needed):

node path/to/server.js

6. Verify the server is up by querying its exposed MCP endpoints using your MCP client tooling. Ensure your environment variables are set according to your chosen authentication mode.

Notes and tips:

• If you’re using interactive mode and running locally, you may see device-code or browser login prompts in your MCP client UI.
• For app-only (client_credentials) mode, ensure your Azure AD app has Calendars.ReadWrite, People.Read.All, and User.ReadBasic.All permissions and that admin consent has been granted.
• The get-event, list-events, and update-event calls will reflect changes in Microsoft Graph calendars and return updated event data including IDs and URLs.
• When using update-event-attendees, you can add or remove attendees in a single operation to keep the event attendees in sync with external systems.
• If you encounter token expiry in client_provided_token mode, manage token refresh externally as described in your integration plan.
• The server is designed to interoperate with other MCP servers (e.g., GitHub MCP server) to tie calendar actions to workflow events like issue creation or PR reviews.