TeamsBridgeMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMS_REGION | No | Chat service region of your tenant. Tenants outside Europe typically use `amer` or `apac`. (Flag: --region) | emea |
| TEAMS_BROWSER | No | Browser for sign-in: `chrome` or `msedge`. (Flag: --browser) | chrome |
| TEAMS_PARTITION | No | Middle-tier partition used for profiles and meetings. Copy it from DevTools. (Flag: --partition) | emea-02 |
| TEAMS_SESSION_FILE | No | Different session location. (Flag: --session-file) | data/session.json |
| TEAMS_ONEDRIVE_HOST | No | Your OneDrive host, e.g. `contoso-my.sharepoint.com`. Required for `upload_file`. Open OneDrive in the browser and copy the host from the address bar. (Flag: --onedrive-host) | |
| TEAMS_ENDPOINTS_FILE | No | Your own registry file. (Flag: --endpoints-file) | data/endpoints.json |
| TEAMS_CHAT_FILES_FOLDER | No | OneDrive folder Teams uses for chat uploads. It is localized, e.g. `Microsoft Teams-Chatdateien` in German. (Flag: --chat-files-folder) | Microsoft Teams Chat Files |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| teams_statusC | Check Teams session export and endpoint registry status |
| teams_loginA | Open Chrome on Teams so the user can sign in; the session is saved automatically. Returns immediately, check teams_status afterwards. |
| list_chatsB | List recent conversations (chats, meeting chats, channels) of the signed-in user, newest activity first |
| list_channelsB | List your teams and their channels (channel id works with list_messages and send_message) |
| list_messagesC | List messages of a channel or chat conversation |
| send_messageB | Send a message to a chat or channel; in channels pass replyToMessageId (the thread's root post id) to reply in that thread |
| search_messagesC | Search messages across chats and channels |
| upload_fileA | Send a local file to a chat: uploads it to your OneDrive Teams chat files folder, gives the chat members read access and posts it as a message (like Teams does). Use conversationId '48:notes' to send to yourself. |
| download_fileC | Download a file from a conversation to a local path |
| start_chatA | Start (or reopen) a chat with people by e-mail; returns the conversationId for send_message/upload_file. One person without topic = 1:1 chat (existing one is reused), otherwise a new group chat. |
| list_meetingsB | List meetings in your calendar from now on |
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 11 tools
Each tool targets a distinct Teams resource and action: chats, channels, messages, meetings, files, and session/auth handling. The closest pairs, list_chats vs list_channels and list_messages vs search_messages, are clearly separated by their descriptions and intended use.
Most names follow a readable snake_case verb_noun pattern such as list_chats, send_message, upload_file, and search_messages. The main deviation is teams_status and teams_login using a teams_ prefix instead of a verb, but the convention is still mostly predictable.
Eleven tools is well within a reasonable range for a Teams bridge and each tool maps to a concrete operation. Auth/status, discovery, messaging, files, and meetings are all represented without excessive fragmentation.
The surface covers core workflows: listing chats/channels/messages, sending and searching messages, starting chats, transferring files, and listing meetings. Some gaps remain around message edit/delete, channel creation, meeting creation/details, and member listing, but these are workable for the apparent bridge scope.