"Slack - Team Communication and Collaboration Platform" matching MCP servers:

Enables posting to Slack as a bot or as a specific authorized person, and sending DMs, from any script, agent, or CI job via a local MCP server over stdio.

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

Enables AI agents to communicate with each other through Slack-like room-based channels with messaging, mentions, presence management, and long-polling for real-time collaboration.

Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode auth.

A multi-agent collaborative development bridge that enables TRAE Work to offload complex tasks to Codex executor, with tools for task submission, status tracking, artifact listing, and permission management.

Enables AI agents to read and write Markdown notes in an Obsidian vault over the Model Context Protocol, with concurrency-safe edits and optional write restrictions.

Enables structured role-to-role handoffs and merge gating for multi-agent collaboration. It persists evidence and computes approval gates without invoking LLMs.

An MCP server for team documentation and knowledge bases, enabling semantic search over documentation files using local embeddings.

MCP server that reads Slack through your own browser session, authenticating as you rather than a bot. Provides tools to search messages, retrieve channel/DM/thread history, resolve users, and post messages (write disabled by default).

Lets an AI assistant read and write business records in plain language, including looking up people, creating and updating tasks, logging time, and pulling utilization reports through a synthetic ops platform or an optional ClickUp adapter.

Enables reading Slack channels, messages, and threads using the web interface via a persistent browser session, designed for guest users without API access. Does not send messages.

A read-only MCP server for Slack that reads messages from channels the bot is invited to, without storing data. It provides tools to fetch channel history, thread replies, and resolve user IDs, with access controlled solely by channel invitations.

A self-hosted, read-only Slack MCP server that runs locally and provides read-only access to Slack channels, messages, and users via the Slack Web API, with no third-party intermediary.

MCP server for Argo CD and Vault that allows authenticated users to run CLI commands via GitLab SSO, with confirmation for dangerous operations and secret redaction from model context.

MCP server that connects Claude Code to Slack, allowing two-way communication via Slack Socket Mode without tunnels.

Local MCP stdio bridge to Slack's hosted MCP server, enabling agents to use Slack tools (send messages, search, history, canvas, etc.) via local OAuth and token refresh.

An MCP server that enables AI agents to read and write Slack messages as the user, not as a bot, using Slack user tokens for authentic actions across multiple workspaces.

MCP server for team task tracking, code review, and activity monitoring via Claude Code. Assign tasks, track branch activity, review code, and get daily summaries through natural language.

Enables interaction with the Flow Team API through MCP clients, allowing endpoint discovery, API calls, and project management operations like listing projects and participants.

Enables IDE plugins to authenticate and communicate with the YAAIF platform via MCP, bridging Cursor, VS Code, IntelliJ, Claude Code, Codex, and OpenCode.