MCP Microsoft Teams Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAM_ID | Yes | MS Teams Group Id or Team Id | |
| TEAMS_APP_ID | Yes | UUID for your MS Entra ID application ID | |
| TEAMS_APP_TYPE | Yes | SingleTenant or MultiTenant | |
| TEAMS_CHANNEL_ID | Yes | MS Teams Channel ID with url escaped chars | |
| TEAMS_APP_PASSWORD | Yes | Client secret | |
| TEAMS_APP_TENANT_ID | No | Tenant uuid in case of SingleTenant |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_threadA | Start a new thread with a given title and content |
| update_threadB | Update an existing thread with new content |
| read_threadA | Read replies in a thread |
| list_threadsA | List threads in channel with pagination |
| get_member_by_nameB | Get a member by its name |
| list_membersA | List all members in the team |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource-action pair: thread lifecycle (start/update/read/list) and member lookup (get by name/list). There is no meaningful overlap, and the descriptions make the boundary between read_thread and list_threads clear.
All tools follow a consistent snake_case verb_noun pattern such as start_, update_, read_, list_, and get_. The verb choices are predictable and match the operation being performed.
Six tools is well-scoped for a Teams server covering thread management and member lookup. There are no redundant tools, and the set feels appropriately sized for its stated domain.
Threads have start, read, update, and list coverage, while members have get and list coverage. Missing thread deletion and explicit reply/send-message operations are minor gaps, but the core workflows agents would likely need are covered.