AI-native Microsoft Teams integration — read chats, send messages, search people
Microsoft Teams API MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. AI-native Microsoft Teams integration — read chats, send messages, search people.
AI-native Microsoft Teams integration — read conversations, send messages, and manage members via the Teams Chat Service REST API.
Once Microsoft Teams API is connected, these are the calls the assistant has available:
Flag — DescriptionPrerequisites — The Prerequisites tool exposed by this serverExamples — The Examples tool exposed by this serverteams-api on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 8 environment variables: TEAMS_LOGIN, TEAMS_TOKEN, TEAMS_BEARER_TOKEN, TEAMS_SUBSTRATE_TOKEN, TEAMS_REGION, TEAMS_AGENT_MARKER, TEAMS_DELETE_MODE, TEAMS_DELETE_TOMBSTONE. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
npx, which all MCP and CLI commands use.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. Microsoft Teams API's toolset — Flag, Prerequisites, Examples — is a fair guide to whether it matches your workflow. It is maintained by Maxim-Mazurok; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Flag | Description |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Examples | The Examples tool exposed by this server. |
{
"mcpServers": {
"teams-api": {
"command": "npx",
"args": ["-y", "teams-api"],
"env": {
"TEAMS_LOGIN": "your-value",
"TEAMS_TOKEN": "your-value",
"TEAMS_BEARER_TOKEN": "your-value",
"TEAMS_SUBSTRATE_TOKEN": "your-value",
"TEAMS_REGION": "your-value",
"TEAMS_AGENT_MARKER": "your-value",
"TEAMS_DELETE_MODE": "your-value",
"TEAMS_DELETE_TOMBSTONE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
npx, which all MCP and CLI commands use.| Variable | Description | Required |
|---|---|---|
| TEAMS_LOGIN | Configuration value read at startup. | Optional |
| TEAMS_TOKEN | Credential the server authenticates with. | Yes |
| TEAMS_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| TEAMS_SUBSTRATE_TOKEN | Credential the server authenticates with. | Yes |
| TEAMS_REGION | Configuration value read at startup. | Optional |
| TEAMS_AGENT_MARKER | Configuration value read at startup. | Optional |
| TEAMS_DELETE_MODE | Configuration value read at startup. | Optional |
| TEAMS_DELETE_TOMBSTONE | 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.