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 fieldWordPress Remote MCPWatchlist candidateSlack MCP ServerMCP100 Selected
Task fit
Best for
  • WordPress developers/operators who need a remote MCP proxy to a WordPress site using the site's existing user/capability model.
  • 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
Not ideal for
  • Users who want a zero-configuration hosted WordPress service or who cannot safely grant the AI client the underlying WordPress account's capabilities.
  • Bulk Slack export or archival
  • Unattended messaging, channel creation, or canvas modification
Avoid when
  • Avoid using a highly privileged WordPress administrator account when lower-privilege credentials can satisfy the workflow.
  • 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
Provenance
Provenance details

Ecosystem official

github:automattic · Publisher source ↗

First-party MCP

Slack · Publisher source ↗

Maintenance
Maintenance details

Stale

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth 2.1 with PKCE is the preferred path; reviewed alternatives include JWT and WordPress Application Passwords.Slack 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.
CostOpen-source proxy; WordPress hosting/plugins/services and AI/model costs can still apply.Slack 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.
PermissionsEffective permissions follow the authenticated WordPress user and the abilities exposed by the backend MCP Adapter.Slack 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.
Data handlingWordPress content, metadata and action results can transit the proxy and connected AI client/provider. OAuth tokens are stored locally by the proxy and must be protected.Searches, 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.
Limitations
Tradeoffs
  • Official WordPress MCP adapter is promising and ecosystem-significant, but self-hosted/plugin-dependent maturity and ability scoping need more evidence.
  • 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.
Risk contextA high-privilege WordPress user can expose broad content/site administration authority to the AI client.Slack 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.
Evidence date
Editorial review2026-09-13T00:00:00Z2026-07-24
Candidate evidence2026-09-13T00:00:00Z2026-07-29T20:58:26.000Z

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

Read the evidence method →