The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Data & research · SKILL.md

local-mcp-teamchat

local-mcp-teamchat

Use when the user wants to read or search Microsoft Teams or Slack on macOS or Windows, including channels and DMs. Powered by LMCP, reading the desktop apps' local data.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: local-mcp-teamchat description: Use when the user wants to read or search Microsoft Teams or Slack on macOS or Windows, including channels and DMs. Powered by LMCP, reading the desktop apps' local data.

Teams & Slack via LMCP

LMCP reads the Microsoft Teams and Slack desktop apps' local data on the user's computer (macOS and Windows), so reading needs no Slack token. Sending to Teams is different: teams_send_channel_message (and teams_send_message on Windows) goes through Microsoft Graph and needs connect_m365_account.

Core tools

  • Teams: teams_list_teams, teams_list_channels, teams_list_chats, teams_read_channel_messages, teams_read_chat_messages; send via teams_send_message / teams_send_channel_message (preview-before-send).
  • Slack: slack_list_workspaces, slack_list_channels, slack_read_channel_messages, slack_search_messages.

Good practice

  • Reading comes from the desktop app's synced data; summarize threads rather than dumping every message.
  • For "what did the team decide about X", use teams_read_channel_messages / slack_search_messages.
  • These read the local app's synced store — if a tool reports not-synced/not-set-up, the user needs the Teams/Slack desktop app installed and signed in; relay that instead of retrying.
  • Any send is preview-first: show the channel + text, confirm, then send.
Saved skills