Automate Microsoft Teams Communications

Automates Microsoft Teams operations - posting channel messages, sending chat messages, scheduling online meetings, managing teams/channels, and searching messages - through Composio's Microsoft Teams toolkit exposed via Rube MCP. It documents exact tool sequences, required parameters, and the ID-format and rate-limit pitfalls needed to drive Teams correctly.

Use this skill when a task requires posting a Teams channel message, sending a direct or group chat message, scheduling a Teams meeting, listing/creating/managing teams and channels, or searching messages across chats and channels. It assumes Rube MCP is already connected (RUBE_SEARCH_TOOLS available) and the Microsoft Teams connection is ACTIVE via RUBE_MANAGE_CONNECTIONS - always call RUBE_SEARCH_TOOLS first for current schemas.

Setup: add https://rube.app/mcp as an MCP server (no API keys needed), verify RUBE_SEARCH_TOOLS responds, call RUBE_MANAGE_CONNECTIONS with toolkit microsoft_teams, complete the Microsoft OAuth link if not ACTIVE.

Five core workflows: Channel messages - TEAMS_LIST then TEAMS_LIST_CHANNELS to resolve team_id (UUID) and channel_id (thread format like 19:abc@thread.tacv2) before TEAMS_POST_CHANNEL_MESSAGE, watching for pagination via @odata.nextLink, 403s from missing team access, and a roughly 28KB message size limit. Chat messages - CHATS_GET_ALL_CHATS/LIST_USERS/TEAMS_CREATE_CHAT to resolve or create a chat_id, noting that CREATE_CHAT requires the authenticated user among members, one-on-one chats return the existing chat if one already exists, and group chats need an 'owner'-role member. Online meetings - LIST_USERS then CREATE_MEETING with ISO 8601 start/end times and participant user IDs (GUIDs, not emails); this creates a standalone meeting, not a calendar event (use OUTLOOK_CALENDAR_CREATE_EVENT with is_online_meeting=true for that). Team/channel management - TEAMS_LIST, GET_TEAM, LIST_CHANNELS, GET_CHANNEL, CREATE_CHANNEL, LIST_TEAM_MEMBERS, ADD_MEMBER_TO_TEAM, always sourcing IDs from list operations rather than guessing formats. Search messages - SEARCH_MESSAGES with KQL syntax (from:, sent:, attachments, boolean logic), noting search is eventually consistent with a 30-60 second indexing delay.

Common patterns: resolving team/channel IDs by listing then filtering by displayName; resolving user IDs the same way for meeting participants or chat members; and pagination via @odata.nextLink for teams/users or a top parameter (max 50) for chats.

Known pitfalls preserved from the source: different operations require different Microsoft Graph permissions, and some need admin consent in the Azure AD tenant; ID formats vary by entity (team UUIDs, thread-format channel/chat IDs, user GUIDs) and must always be resolved from list operations, never guessed; Microsoft Graph throttling returns 429 with a Retry-After header, requiring exponential backoff and batching to reduce request volume; and message formatting is capped around 28KB, requiring long content to be split.

Runs entirely through Rube MCP (https://rube.app/mcp) and Composio's Microsoft Teams toolkit built on Microsoft Graph - RUBE_SEARCH_TOOLS for schema discovery and RUBE_MANAGE_CONNECTIONS for the Microsoft OAuth connection, with a related handoff to OUTLOOK_CALENDAR_CREATE_EVENT for calendar-linked meetings.

IT/ops teams and automation builders who need to drive Microsoft Teams messaging, meeting scheduling, and team/channel management through Composio/Rube MCP tools correctly - especially around the ID-resolution, permission, and rate-limit quirks that are easy to get wrong from the raw Microsoft Graph API alone.