Claude project management, wired into your real projects
MCP is Anthropic’s open standard, and Claude speaks it natively — so connecting Claude to AB Projects takes one command. From then on Claude works on the same tasks and documents your team sees in Microsoft Teams, instead of guessing from what you paste in.
Last updated: 19 July 2026
Connect Claude in one step
Pick whichever surface you work in. Both point at the same MCP server, and both authenticate with Microsoft 365.
Claude Code
Run this once in your terminal — HTTP transport, no config file to edit.
Claude Desktop
Add the endpoint as a connector, or edit claude_desktop_config.json:
The first time Claude calls a tool, your browser opens to sign in with Microsoft 365 — there is no API key to create or rotate. You will need AB Projects in your tenant first; it installs from Microsoft AppSource and is free for up to 10 users. Full walkthrough: Connecting AI assistants via MCP.
What Claude can reach once connected
These are the tools AB Projects publishes over MCP — see the full tools reference for the exact list.
Tasks
Find what is assigned to you, search across projects, read a task in full, create new work, change dates, owners and status, close things out, and leave comments as you.
Projects
See which projects you belong to, who else is on them, the options each project defines, and the schedule — so Claude reasons about your workspace, not a generic one.
Wiki documents
Walk the document tree, open and search articles, draft new pages, revise existing ones and comment — useful for turning a long Claude session into a written decision record.
Prompts that pay off
Claude’s longer context suits multi-step work — reading a document and reconciling it with the task list, for example.
Least privilege, and a record of everything
Microsoft 365 OAuth
You sign in with your existing Microsoft 365 account. No API keys are issued, stored or rotated.
Your permissions only
Claude inherits exactly the access you have in the web app — it cannot open a project you cannot.
Audit log
Every action is recorded with the reason Claude gave, so you can review what the assistant did and why.
Team stays informed
Each change posts an Adaptive Card to the project channel, so nothing done in Claude is invisible in Teams.
Frequently asked questions
How do I connect Claude to AB Projects?
In Claude Code, run a single claude mcp add command pointing at the AB Projects MCP endpoint. In Claude Desktop, add the same endpoint as a connector or put it in claude_desktop_config.json. Both then sign in with Microsoft 365 the first time Claude calls a tool.
Does this work in Claude Code as well as the Claude app?
Yes. Claude Code connects over HTTP transport from the terminal, and Claude Desktop connects through its connector settings or config file. Both talk to the same AB Projects MCP server, so you get the same tools either way.
What can Claude actually change?
Claude can look up and search your tasks, create and update them, complete them and add comments, list projects and members, check schedules, and read, write and comment on project wiki documents — all as you, with your permissions.
Is my data safe when Claude has access?
Claude authenticates with Microsoft 365 OAuth and inherits exactly the permissions you already have — no API keys, and no access to projects you cannot open yourself. Every action Claude takes is written to the audit log with the reason it gave, and posted to the project channel in Microsoft Teams.
Why MCP rather than a custom plugin?
MCP is an open standard, so the same AB Projects server works with Claude, ChatGPT, Gemini, Cursor, Copilot and other clients. You can change assistant without rebuilding the integration.
Give Claude something real to work on
Free for up to 10 users. Explore AB Projects, see how MCP works, or set up ChatGPT the same way.