# How to connect Microsoft Teams to Grok Bot (no API keys) > Connect Microsoft Teams to Grok Bot with ClawLink in one click — 153 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/microsoft-teams Grok Bot runs on its own cloud computer, so most Microsoft Teams guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Microsoft Teams setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Microsoft Teams actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect microsoft-teams` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Microsoft Teams. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Microsoft Teams** — `npx -y @useclawlink/cli connect microsoft-teams`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect microsoft-teams # connect Microsoft Teams (browser OAuth) npx -y @useclawlink/cli actions microsoft-teams # list available actions npx -y @useclawlink/cli run microsoft-teams --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect microsoft-teams ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Microsoft Teams to chats get all chats and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Microsoft Teams is connected in the dashboard, that agent calls the same 153 Microsoft Teams tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Microsoft Teams MCP for Grok Bot Looking for a Microsoft Teams MCP server for Grok Bot? ClawLink connects Microsoft Teams to Grok Bot and exposes 153 Microsoft Teams tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Microsoft Teams integration](https://claw-link.dev/openclaw/microsoft-teams) and the [Hermes Microsoft Teams integration](https://claw-link.dev/hermes/microsoft-teams) connect the same ClawLink account the same way. ## What the Grok Bot Microsoft Teams integration can do 153 Microsoft Teams tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 153. ### 30 of 153 Microsoft Teams tools for Grok Bot | Tool | What it does | |---|---| | **Chats get all chats** `microsoft_teams_chats_get_all_chats` | Retrieve all chats a user is part of | | **Create meeting** `microsoft_teams_create_meeting` | Create a new online meeting | | **Get channel** `microsoft_teams_get_channel` | Get details of a specific channel within a team | | **Get chat** `microsoft_teams_get_chat` | Get details of a specific chat | | **Get my profile** `microsoft_teams_get_my_profile` | Get the current user's Teams profile | | **Get online meeting** `microsoft_teams_get_online_meeting` | Get details of a specific online meeting | | **Get shift** `microsoft_teams_get_shift` | Get details of a specific shift | | **Get team from group** `microsoft_teams_get_team_from_group` | Get team details from a group ID | | **List associated teams** `microsoft_teams_list_associated_teams` | List teams that a user is associated with (direct or shared channel) | | **List channel tabs** `microsoft_teams_list_channel_tabs` | List tabs configured in a channel | | **List online meetings** `microsoft_teams_list_online_meetings` | List online meetings | | **List shifts** `microsoft_teams_list_shifts` | List shifts in a team schedule | | **List team members** `microsoft_teams_list_team_members` | List members of a team | | **List user chat messages** `microsoft_teams_list_user_chat_messages` | List messages in a user chat | | **List user joined teams** `microsoft_teams_list_user_joined_teams` | List the Teams that a specified user is a direct member of | | **Get call operation** `microsoft_teams_get_call_operation` | Get a specific commsOperation for a call | | **Get channel message** `microsoft_teams_get_channel_message` | Retrieves a specific message from a Microsoft Teams channel using its Team, Channel, and | | **Get channel message reply** `microsoft_teams_get_channel_message_reply` | Retrieve a single reply to a message in a channel | | **Get chat member** `microsoft_teams_get_chat_member` | Get a specific conversation member from a Microsoft Teams chat | | **Get chat message** `microsoft_teams_get_chat_message` | Get a specific chat message | | **Get day note** `microsoft_teams_get_day_note` | Retrieve a specific day note from a team's schedule | | **Get files folder** `microsoft_teams_get_files_folder` | Get the files folder (DriveItem) metadata for a specific channel in a Microsoft Teams team | | **Get meeting transcript content** `microsoft_teams_get_meeting_transcript_content` | Retrieve the raw text/vtt content for a Microsoft Teams meeting transcript | | **Get offer shift request** `microsoft_teams_get_offer_shift_request` | Get a specific offer shift request from a Microsoft Teams schedule | | **Get open shift** `microsoft_teams_get_open_shift` | Get a specific open shift from a Microsoft Teams schedule | | **Get open shift change request** `microsoft_teams_get_open_shift_change_request` | Retrieve a specific open shift change request from a Microsoft Teams team's schedule | | **Get presence** `microsoft_teams_get_presence` | Get a specific user's presence information | | **Get primary channel** `microsoft_teams_get_primary_channel` | Get the default (General) channel of a team | | **Get schedule** `microsoft_teams_get_schedule` | Retrieve the properties and relationships of a schedule object | | **Get scheduling group** `microsoft_teams_get_scheduling_group` | Retrieve a specific scheduling group from a Microsoft Teams team's schedule | ## Example prompts **Chats Get All Chats** > Use Microsoft Teams to chats get all chats and walk me through the result in plain English. **Create Meeting** > Create it in Microsoft Teams for me, then confirm the important fields before you finish. **Get Channel** > Pull the relevant data from Microsoft Teams, summarize it in plain English, and point out anything that needs attention. **Get Chat** > Pull the relevant data from Microsoft Teams, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Microsoft Teams working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Microsoft Teams app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Microsoft Teams through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Microsoft Teams. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Microsoft Teams actions to the runtime in a format your agent can reliably use. | 153 tools for Microsoft Teams are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Microsoft Teams to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Microsoft Teams in the browser, and the 153 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Microsoft Teams from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Microsoft Teams tools Microsoft Teams tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Microsoft Teams call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Microsoft Teams returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Microsoft Teams and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Microsoft Teams integration? Yes. ClawLink is the fastest way to connect Grok Bot to Microsoft Teams: link your Microsoft Teams account once in the browser and Grok Bot can call the Microsoft Teams API through 153 ready-made tools — no custom code or token handling. ### How do I connect Microsoft Teams to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect microsoft-teams` to authorize Microsoft Teams. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Microsoft Teams to Grok Bot? About two minutes. Sign in, click Connect next to Microsoft Teams in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Microsoft Teams up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Microsoft Teams working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Outlook tools](https://claw-link.dev/grokbot/outlook) — Read mail, manage calendar, and browse contacts - [Connect SharePoint](https://claw-link.dev/grokbot/sharepoint) — Browse sites, lists, and files in SharePoint - [Microsoft OneDrive tools](https://claw-link.dev/grokbot/onedrive) — Browse, search, and manage OneDrive files