Interact with Microsoft Teams to read, create, and reply to messages, and mention members.
Microsoft Teams MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Interact with Microsoft Teams to read, create, and reply to messages, and mention members.
Please read this document to help you to configure Microsoft Teams and required Azure resources. It is not a step-by-step guide but can help you figure out what you will need.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Microsoft Teams MCP is connected, these are the calls the assistant has available:
Key — DescriptionTEAMS_APP_ID — UUID for your MS Entra ID application IDTEAMS_APP_PASSWORD — Client secretTEAMS_APP_TYPE — SingleTenant or MultiTenantTEAMS_APP_TENANT_ID — Tenant uuid in case of SingleTenantTEAM_ID — MS Teams Group Id or Team IdTEAMS_CHANNEL_ID — MS Teams Channel ID with url escaped charsYou will need 6 environment variables: TEAMS_APP_ID, TEAMS_APP_TENANT_ID, TEAM_ID, TEAMS_CHANNEL_ID, TEST_THREAD_ID, TEST_MESSAGE_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Microsoft Teams MCP's toolset — Key, TEAMS_APP_ID, TEAMS_APP_PASSWORD and 4 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Key | Description |
| TEAMS_APP_ID | UUID for your MS Entra ID application ID |
| TEAMS_APP_PASSWORD | Client secret |
| TEAMS_APP_TYPE | SingleTenant or MultiTenant |
| TEAMS_APP_TENANT_ID | Tenant uuid in case of SingleTenant |
| TEAM_ID | MS Teams Group Id or Team Id |
| TEAMS_CHANNEL_ID | MS Teams Channel ID with url escaped chars |
{
"mcpServers": {
"github-com-inditextech-mcp-teams-server": {
"command": "docker",
"args": ["run", "-i", "--rm", "inditextech/mcp-teams-server"],
"env": {
"TEAMS_APP_ID": "your-value",
"TEAMS_APP_TENANT_ID": "your-value",
"TEAM_ID": "your-value",
"TEAMS_CHANNEL_ID": "your-value",
"TEST_THREAD_ID": "your-value",
"TEST_MESSAGE_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TEAMS_APP_ID | Configuration value read at startup. | Optional |
| TEAMS_APP_TENANT_ID | Configuration value read at startup. | Optional |
| TEAM_ID | Configuration value read at startup. | Optional |
| TEAMS_CHANNEL_ID | Configuration value read at startup. | Optional |
| TEST_THREAD_ID | Configuration value read at startup. | Optional |
| TEST_MESSAGE_ID | 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.