Connect your AI Agents to Microsoft Planner in minutes

What is a Microsoft Planner MCP?

It's an MCP server that connects your agents to Microsoft Planner via tools. Your agents can invoke these tools to create and assign tasks, organize work into buckets, update task progress, retrieve plan details, and more.

Microsoft doesn't offer an MCP server purpose built for Microsoft Planner, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Microsoft Planner MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated task creation from external events: When a new support ticket is opened in Zendesk, an agent creates a corresponding task in Microsoft Planner, assigns it to the right team member, and sets a due date based on the ticket's priority level

• Sprint status digest: On a recurring schedule, an agent retrieves all tasks across a Planner plan, groups them by bucket and completion status, and posts a structured summary to a Microsoft Teams channel so the team has a current snapshot without opening Planner

• Cross-tool project kickoff: When a deal closes in Salesforce, an agent creates a new plan in Planner, populates it with a standard set of onboarding tasks, and assigns each task to the appropriate owner based on role

• Overdue task escalation: An agent scans open Planner tasks each morning, identifies items past their due date with no recent progress update, and posts a targeted reminder in Slack to each assigned team member

What are popular tools for Microsoft Planner's MCP server?

Here are some of the most commonly used tools:

• list_plans: retrieves all Planner plans associated with a Microsoft 365 group. Useful for agents that need to identify which plan to target before creating or updating tasks

• create_task: adds a new task to a specified plan and bucket with a title, due date, and assignee. Call this when an agent needs to create work items in response to events in other systems

• get_task: fetches the full details of a single task including assignments, checklist items, and notes. Use this when an agent needs complete context on a task before modifying it or surfacing it in a report

• update_task: modifies an existing task's fields such as percent complete, due date, or assigned users. Good for workflows that keep Planner tasks synchronized with status changes happening in external tools

• list_tasks: retrieves all tasks in a plan, optionally filtered by bucket or assignee. Helpful when an agent needs to audit task distribution, generate a progress report, or identify overdue items

• list_buckets: returns all buckets within a plan, providing the structural context an agent needs before routing new tasks to the correct category or stage

What makes Merge Agent Handler's Microsoft Planner MCP server better than alternative Microsoft Planner MCP servers?

Here is what sets Merge Agent Handler's Microsoft Planner MCP server apart from building your own or using a standalone alternative:

• Enterprise-grade security and DLP: Merge Agent Handler includes data loss prevention controls that filter specific fields before they reach an agent. For Microsoft Planner, this means task notes, attachments, and assignee details can be blocked at the tool layer even when the agent has broad plan access

• Managed authentication and credentials: Merge stores your Microsoft 365 OAuth credentials and handles token refresh automatically. You never pass raw credentials to an agent or coordinate re-authentication when tokens expire

• Real-time observability and audit trail: Every tool call made against Microsoft Planner is logged with timestamp, tool name, input parameters, and response metadata. You can see exactly which tasks an agent created, updated, or read without adding any custom instrumentation

• Tool Packs and controlled access: Tool Packs let you combine specific Microsoft Planner tools with tools from other connectors into a single scoped MCP endpoint. An agent gets exactly the operations it needs for a given workflow, nothing beyond that

How can I start using Merge Agent Handler's Microsoft Planner MCP server?

You can take the following steps (assuming you use Claude Code):

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Microsoft Planner and complete the OAuth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Microsoft Planner data directly. The first time you use a Microsoft Planner tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Microsoft Planner MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge Agent Handler to connect their AI tools to Microsoft Planner?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Microsoft Planner without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity. A project manager can ask their AI to create tasks, check plan status, or reassign work across buckets, all within the permissions IT has defined.

IT also provisions access by role or group via SCIM. A project manager, for example, gets Microsoft Planner access to create and track tasks, Jira to log related engineering work, and Slack to coordinate team updates; while a team lead gets Microsoft Planner access to monitor plan progress, Asana to manage cross-team dependencies, and Microsoft Teams to report status to stakeholders.

Every tool call an employee's AI makes to Microsoft Planner is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.