Teams MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check the authentication status of the Microsoft Graph connection. Returns whether the user is authenticated and shows their basic profile information. |
| get_current_userA | Get the current authenticated user's profile information including display name, email, job title, and department. |
| search_usersA | Search for users in the organization by name or email address. Returns matching users with their basic profile information. |
| get_userC | Get detailed information about a specific user by their ID or email address. Returns profile information including name, email, job title, and department. |
| list_teamsA | List all Microsoft Teams that the current user is a member of. Returns team names, descriptions, and IDs. |
| list_channelsB | List all channels in a specific Microsoft Team. Returns channel names, descriptions, types, and IDs for the specified team. |
| get_channel_messagesC | Retrieve recent messages from a specific channel in a Microsoft Team. Returns message content, sender information, and timestamps. |
| send_channel_messageC | Send a message to a specific channel in a Microsoft Team. Supports text and markdown formatting, mentions, and importance levels. |
| get_channel_message_repliesC | Get all replies to a specific message in a channel. Returns reply content, sender information, and timestamps. |
| reply_to_channel_messageB | Reply to a specific message in a channel. Supports text and markdown formatting, mentions, and importance levels. |
| list_team_membersB | List all members of a specific Microsoft Team. Returns member names, email addresses, roles, and IDs. |
| search_users_for_mentionsA | Search for users to mention in messages. Returns users with their display names, email addresses, and mention IDs. |
| list_chatsB | List all recent chats (1:1 conversations and group chats) that the current user participates in. Returns chat topics, types, and participant information. |
| get_chat_messagesB | Retrieve recent messages from a specific chat conversation. Returns message content, sender information, and timestamps. |
| send_chat_messageC | Send a message to a specific chat conversation. Supports text and markdown formatting, mentions, and importance levels. |
| create_chatC | Create a new chat conversation. Can be a 1:1 chat (with one other user) or a group chat (with multiple users). Group chats can optionally have a topic. |
| search_messagesA | Search for messages across all Microsoft Teams channels and chats using Microsoft Search API. Supports advanced KQL syntax for filtering by sender, mentions, attachments, and more. |
| get_recent_messagesC | Get recent messages from across Teams with advanced filtering options. Can filter by time range, scope (channels vs chats), teams, channels, and users. |
| get_my_mentionsA | Find all recent messages where the current user was mentioned (@mentioned) across Teams channels and chats. |
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 19 tools
Most tools have distinct purposes targeting specific resources like channels, chats, users, or messages, but there is some overlap: get_recent_messages and search_messages both retrieve messages with filtering, which could cause confusion. However, descriptions clarify that get_recent_messages focuses on recent messages with time/scope filters, while search_messages uses advanced KQL syntax, helping to differentiate them.
Tool names follow a highly consistent verb_noun pattern throughout, such as list_teams, get_channel_messages, send_chat_message, and search_users. All tools use snake_case with clear verbs like get, list, create, send, reply, and search, making the set predictable and easy to understand.
With 19 tools, the count is slightly high but reasonable for a comprehensive Teams integration covering authentication, chats, channels, messages, users, and search. It provides broad functionality without being overwhelming, though it could be streamlined by merging some overlapping tools like get_recent_messages and search_messages.
The toolset offers complete coverage for Microsoft Teams interactions, including CRUD operations for messages (send, reply, get), resource listing (teams, channels, chats, members), user management (get, search), and authentication. There are no obvious gaps; agents can perform core workflows like messaging, searching, and team management effectively.