# How to connect Microsoft Teams to OpenClaw (no API keys) > Connect Microsoft Teams to OpenClaw with ClawLink in one click — 15 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/microsoft-teams The usual route to Microsoft Teams access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Microsoft Teams setup: install one ClawHub skill, connect Microsoft Teams in the browser, and OpenClaw can call real Microsoft Teams actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Microsoft Teams MCP for OpenClaw Looking for a Microsoft Teams MCP server for OpenClaw? ClawLink connects Microsoft Teams to OpenClaw and exposes 15 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 Hermes instead? The [Hermes Microsoft Teams integration](https://claw-link.dev/hermes/microsoft-teams) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/microsoft-teams ## Setup It takes three steps to connect OpenClaw to Microsoft Teams. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Microsoft Teams** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```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) ``` ## What the OpenClaw Microsoft Teams integration can do 15 Microsoft Teams tools are ready for OpenClaw once the account is connected. ### All 15 Microsoft Teams tools for OpenClaw | Tool | What it does | |---|---| | **List user joined teams** `microsoft_teams_list_user_joined_teams` | List the Teams that a specified user is a direct member of | | **List associated teams** `microsoft_teams_list_associated_teams` | List teams that a user is associated with (direct or shared channel) | | **Get team from group** `microsoft_teams_get_team_from_group` | Get team details from a group ID | | **Get channel** `microsoft_teams_get_channel` | Get details of a specific channel within a team | | **List channel tabs** `microsoft_teams_list_channel_tabs` | List tabs configured in a channel | | **Chats get all chats** `microsoft_teams_chats_get_all_chats` | Retrieve all chats a user is part of | | **Get chat** `microsoft_teams_get_chat` | Get details of a specific chat | | **List user chat messages** `microsoft_teams_list_user_chat_messages` | List messages in a user chat | | **List online meetings** `microsoft_teams_list_online_meetings` | List online meetings | | **Get online meeting** `microsoft_teams_get_online_meeting` | Get details of a specific online meeting | | **Create meeting** `microsoft_teams_create_meeting` | Create a new online meeting | | **List team members** `microsoft_teams_list_team_members` | List members of a team | | **Get my profile** `microsoft_teams_get_my_profile` | Get the current user's Teams profile | | **List shifts** `microsoft_teams_list_shifts` | List shifts in a team schedule | | **Get shift** `microsoft_teams_get_shift` | Get details of a specific shift | ## Example prompts **List User Joined Teams** > List the relevant items in Microsoft Teams, group them by priority, and recommend what OpenClaw should do next. **List Associated Teams** > List the relevant items in Microsoft Teams, group them by priority, and recommend what OpenClaw should do next. **Get Team From Group** > Pull the relevant data from Microsoft Teams, summarize it in plain English, and point out anything that needs attention. **Get Channel** > 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 OpenClaw. 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. | 15 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 OpenClaw users instead. You install the plugin once, connect Microsoft Teams in the browser, and the 15 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. ### OpenClaw installed the Microsoft Teams skill but can't call the tools The ClawHub skill teaches OpenClaw about Microsoft Teams, but the calls run through the ClawLink plugin and your connected account. Make sure Microsoft Teams is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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 OpenClaw Microsoft Teams integration? Yes. ClawLink is the fastest way to connect OpenClaw to Microsoft Teams: link your Microsoft Teams account once in the browser and OpenClaw can call the Microsoft Teams API through 15 ready-made tools — no custom code or token handling. ### How do I add Microsoft Teams to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Microsoft Teams skill from ClawHub, then you click Connect in the dashboard to authorize Microsoft Teams. OpenClaw calls the tools from the next message — no config files or API keys. ### How long does it take to connect Microsoft Teams to OpenClaw? About two minutes. Sign in, click Connect next to Microsoft Teams in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Microsoft Teams working from chat. ### OpenClaw installed the Microsoft Teams skill but can't call the tools The ClawHub skill teaches OpenClaw about Microsoft Teams, but the calls run through the ClawLink plugin and your connected account. Make sure Microsoft Teams is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Microsoft OneDrive](https://claw-link.dev/openclaw/onedrive) — Browse, search, and manage OneDrive files - [Connect Outlook](https://claw-link.dev/openclaw/outlook) — Read mail, manage calendar, and browse contacts - [OpenClaw Dynamics 365 integration](https://claw-link.dev/openclaw/dynamics-365) — Manage CRM and ERP data in Dynamics 365