Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldSlack MCP ServerMCP100 SelectedWindows-MCPMCP100 Selected
Task fit
Best for
  • Searching approved Slack channels, messages, files, users, and emoji
  • Reading project conversations and threads from an MCP client
  • Drafting or sending messages and managing canvases with explicit user approval
  • Using an AI client to inspect and operate Windows applications when no safer application API exists
Not ideal for
  • Bulk Slack export or archival
  • Unattended messaging, channel creation, or canvas modification
  • Deterministic automation that can be implemented through a documented API, CLI, or test framework
Avoid when
  • Private channels, direct messages, files, or user profiles cannot be shared with the external AI client
  • Workspace administrators have not approved the Slack app and MCP integration
  • The agent combines untrusted external content with write-capable Slack tools without isolation
  • The desktop session contains sensitive applications, credentials, messages, or files outside the task
Provenance
Provenance details

First-party MCP

Slack · Publisher source ↗

Community implementation

io.github.CursorTouch · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Aug 1, 2026

Popularity evidence
GitHub starsNot documented

6,749

GitHub stars · checked 2026-08-14T18:46:26.000Z

30-day package downloadsNo reliable download data

40,449

PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • github: repository stars: 6,749Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • PyPI Stats: package downloads: 40,449Non-comparable contextual signal.PyPI Stats: package downloads · Provider last month · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationSlack uses confidential OAuth for MCP clients with a registered fixed Slack app ID and client secret. Cursor's publisher-documented integration uses Slack's fixed client ID and opens an OAuth workspace authorization flow.Stdio has no network listener. Non-loopback HTTP requires an auth key or OAuth unless insecure access is explicitly allowed; IP allowlists, TLS, CORS, and host validation are documented.
CostSlack documents no separate MCP server fee. Access to history, search, apps, administration, and AI-client capabilities depends on the workspace's Slack plan; standard Slack API rate limits apply.The MIT-licensed project lists no MCP fee. Windows, Python, hosting, client, and model costs are separate.
PermissionsSlack maps tools to granular user-token scopes for public/private/DM search, files, channel history, messages, reactions, conversations, canvases, profiles, and member lists. Actions execute on behalf of the authenticated user and remain subject to workspace/app approval, Slack access controls, and IP allowlists.Runs with the invoking user's full Windows permissions, including PowerShell, files, registry, processes, UI input, screenshots, and web scraping; many actions are irreversible.
Data handlingSearches, messages, channel history, file content, canvases, user profiles, and tool outputs flow through Slack's managed MCP endpoint to the configured client and its model provider. Slack audit logs can record MCP activity; client-side retention is governed separately.Processing is local. Telemetry excludes screenshots, state captures, arguments, and outputs but includes status, duration, tool and client information, anonymized sessions, and possibly paths in error messages.
Limitations
Tradeoffs
  • Granular OAuth scopes allow narrow access, but useful cross-workspace search can still reveal highly sensitive conversations.
  • Slack's managed endpoint avoids a local server, while requiring confidential OAuth, a fixed app ID, and an eligible directory-published or internal app.
  • The server includes both read and write tools and is subject to Slack Web API rate limits.
  • General computer-use reaches many applications, but visual automation is brittle and broad input control can produce high-impact unintended actions.
Risk contextSlack may contain private messages, credentials, customer data, files, and regulated communications. Request only required OAuth scopes, use an approved app, review the client/model retention policy, isolate other untrusted MCP sources, audit activity, and confirm every send/create/update action. This review does not claim MCP100 execution testing.It is not sandboxed and can delete files, alter registry or system settings, type into applications, and execute PowerShell. Use a VM or low-privilege account, backups, supervision, loopback binding, and disabled high-risk tools.
Evidence date
Editorial review2026-07-242026-08-11
Candidate evidence2026-07-29T20:58:26.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →