MCP server for Microsoft Graph Teams integration
Most team communication work still happens through a UI a human drives. Teams MCP MCP server moves it into the conversation instead. MCP server for Microsoft Graph Teams integration.
A Model Context Protocol (MCP) server that provides seamless integration with Microsoft Graph APIs, enabling AI assistants to interact with Microsoft Teams, users, chats, files, and organizational data.
The server publishes 2 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverAuthentication — The Authentication tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: AUTH_TOKEN, TEAMS_MCP_READ_ONLY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Teams MCP's toolset — Prerequisites, Authentication — is a fair guide to whether it matches your workflow. It is maintained by floriscornel; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Teams MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Authentication | The Authentication tool exposed by this server. |
{
"mcpServers": {
"teams-mcp": {
"command": "npx",
"args": ["-y", "@floriscornel/teams-mcp@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTH_TOKEN | Credential the server authenticates with. | Yes |
| TEAMS_MCP_READ_ONLY | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.