Our products · AI connector · Microsoft Teams
Teams MCP Server
Give Claude your Microsoft Teams: read, search and reply without leaving the AI.
An open-source Model Context Protocol (MCP) server that connects Claude to Microsoft Teams. Each person signs in with their own Microsoft 365 work account, and Claude can then list teams and channels, read and search messages, and send replies on their behalf.
Open source on GitHub and npm · MIT licence · free
Who it is for
The buyer and the problem
Teams that run on Microsoft 365 and use Claude Code, Claude Desktop or Claude Cowork, and IT teams that want a connector they can read and host themselves.
- Decisions and requests live in Teams channels and chats, out of reach of the AI assistant people work in.
- Catching up means scrolling many channels; answers get copied back and forth by hand.
- Closed connectors are hard to audit, and IT cannot see where messages go.
How it works
Teams MCP Server, step by step
- 01
Install
Run it locally for Claude Code, or host it once for the whole organisation on any Node.js host.
- 02
Sign in
Each person signs in with their own Microsoft 365 work account. There are no shared keys.
- 03
Ask
Ask Claude to summarise a channel, find a message or draft a reply.
- 04
Act
Claude calls Microsoft Graph with that person's own permissions and returns the result.
Features
What it does
- 11 tools: teams, channels, channel messages and thread replies, chats, search and profile
- Works with Claude Code (STDIO) and Claude Desktop or Cowork (HTTP/SSE)
- Multi-tenant: any Microsoft 365 organisation, with isolated tokens per user
- Passes messages through and does not store them
- Token caching with silent refresh, and retries when Microsoft Graph throttles
- TypeScript, MIT licensed, self-hostable
Integrations
Works with
- Microsoft Teams (Microsoft Graph)Available
- Claude CodeAvailable
- Claude Desktop and CoworkAvailable
Under the hood
Where AI is used, and where it is not
The model
No model inside. The person's own Claude does the reading and writing; the server is only the bridge to Teams.
Rules and code
Microsoft Graph delegated permissions decide what each person can see. Nobody sees more through Claude than they see in Teams.
People in the loop
Claude sends a message only when the person asks it to, from their own account.
Use cases
How businesses use Teams MCP Server
Morning catch-up
Ask Claude what changed overnight across your project channels and what needs your reply.
Find the decision
Search every team for the message where a date, price or owner was agreed.
Code to channel
From Claude Code, post a release note or a build result to the team channel.
Hand-over notes
Turn a long thread into a summary with owners and next steps, then reply in the thread.
What it shows about Surge
The capability behind the product
MCP and agent integration
We build the connectors that let AI agents work inside the tools a business already uses.
Enterprise identity done right
Per-user Microsoft 365 sign-in and delegated permissions, the pattern we use for client systems.
Open by default
The code is public, so IT teams can review it and host it themselves.
Related accelerators: Agentic IT support desk with grounded answers and human hand-off · Content & campaign agent for CMS (AEM)
Book a working session
A working session with our architects on one of your use cases. You bring a process and sample documents; we leave you with a scoped plan: model, hosting, integrations, timeline and cost range.