What permission do I need to send Teams channel messages?

You need to run connect_m365_account once and grant the Chat.ReadWrite scope. After that, teams_send_channel_message can post to any channel your Microsoft 365 account can access.

Does my message go through an LMCP server?

No. LMCP runs on your Mac and sends the message directly to Microsoft Graph using your own account. Nothing is stored or relayed through an LMCP cloud server.

Can web AIs like ChatGPT or Claude.ai use this tool?

Yes. Web AIs connect through the LMCP Cloud Relay connector, while desktop clients like Claude Desktop and Cursor auto-configure over local stdio. Both can call teams_send_channel_message.

Yes, LMCP is a free, native macOS MCP server with 150+ tools. There are no API keys to buy and nothing is stored on a server.

Send Teams Channel Messages with AI on Mac

The teams_send_channel_message tool lets your AI assistant post a text message straight into a Microsoft Teams channel from your Mac. Instead of switching to the Teams app, you stay in your AI chat and just say what you want sent. For example, you can type: "Post in the Engineering team's General channel: deploy is done, v3.0.278 is live in production." The AI drafts it, sends it through the Microsoft Graph API, and confirms delivery.

It works through your own Microsoft 365 account. You connect once with connect_m365_account (granting the Chat.ReadWrite scope), and from then on your AI can announce releases, ping a team, or share an update without you leaving the conversation. Download LMCP to get started.

Which AI agents work?

LMCP exposes 150+ tools to any MCP-capable AI. Desktop clients auto-configure over local stdio, while web AIs connect through the LMCP Cloud Relay connector.

Desktop (local stdio, auto-configured): Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed.
Web (via LMCP Cloud Relay connector): ChatGPT, Claude.ai, Grok and Perplexity.

Whichever you use, the same teams_send_channel_message tool is available once LMCP is running.

Automation

Sending a channel message is most powerful when it chains with other tools. Your AI can read your calendar, summarize a meeting note, then post the recap to the channel. Typical chains:

list_calendar_events → draft a standup agenda → teams_send_channel_message to the team channel.
read_email → extract a customer decision → post the summary to the relevant project channel.
teams_list_channels → pick the right channel → send the message there.
run a build or check a PR → announce the result to your engineering channel automatically.

Context

Because LMCP runs on your machine, the AI works with your real Microsoft 365 data — your actual teams, channels and signed-in identity. There's no need to copy channel IDs or paste content back and forth. The AI sees the same Teams you do and posts as you, with the context of your other Mac apps (Mail, Calendar, Notes) feeding into what it writes.

Productivity

Posting a clear update to the right Teams channel usually means switching apps, finding the channel, and typing it out. With teams_send_channel_message, a release announcement or status update goes out in one sentence while you stay focused. Teams who automate standup recaps, deploy notices and meeting summaries save several context switches a day — small interruptions that add up to real focus time over a week.

Privacy & GDPR

Everything runs locally on your Mac. LMCP talks to Microsoft Graph using your own account credentials; your message content is not routed through, copied to, or stored on any LMCP server. There are no shared API keys and nothing is retained in the cloud. This local-first design makes LMCP GDPR-compliant by architecture — your data stays under your control on your own hardware.