Connect Microsoft Planner to Claude Code

Make Claude create tasks and update progress in Microsoft Planner. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Microsoft Planner to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Microsoft Planner, you add a Microsoft Planner MCP server: a small hosted service that exposes Microsoft Planner's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft Planner account. No API keys pasted into config files.

claude mcp add --transport http microsoft-planner https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Microsoft Planner once connected?

Full read-write Planner access lets Claude create tasks in the right plan and bucket, set due dates and assignees, update progress and checklist items, and move tasks across buckets as work advances. The board updates that used to mean clicking through Planner happen where the plan already lives.

Create a task in a specific plan and bucket with a title and due date
Assign or reassign a task to a team member
Move a task between buckets as it progresses
Update task progress to not started, in progress, or completed
Add or check off checklist items on a task
Set or update a task's due date and priority

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft Planner access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Microsoft Planner API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft Planner changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft Planner connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Microsoft Planner connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Microsoft Planner account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Microsoft Planner's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Microsoft Planner?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Microsoft Planner account it signs in with. Revoking access is one click in Microsoft Planner.

More on the Microsoft Planner connector

Microsoft Planner connector for claude.ai Todoist + Claude Code Teamwork + Claude Code Shortcut + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us