Slack MCP Server vs Vexa

A side-by-side look at the Slack MCP Server and Vexa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Slack MCP Server logoSlack MCP ServerCommunication · Local subprocess (stdio)Your complete Slack context for Claude—DMs, channels, threads, search. No OAuth apps, no admin approval. --setup and done, 11 tools, auto-refresh.68GreatAuth: otherVexa logoVexaCommunication · Remote HTTP/SSEMeeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.48FairAuth: not declared

Verdict: choose Slack MCP Server for communication work as a local process; choose Vexa for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Slack MCP Server logoChoose Slack MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like slack_token_status, slack_health_check, slack_refresh_tokens.
Explore Slack MCP Server

Vexa logoChoose Vexa when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: API_KEY, API_BASE, TRANSCRIBE_ENABLED, RUNTIME_BACKEND.
Explore Vexa

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSlack MCP Server logoSlack MCP ServerVexa logoVexa
CategoryCommunicationCommunication
Quality signal68/100 · Great48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthotherNot declared
PricingFreemiumNot declared
Required env varsNone listedAPI_KEYAPI_BASETRANSCRIBE_ENABLEDRUNTIME_BACKEND
Verified ownerCommunity listingCommunity listing
GitHub stars322,905
Directory activity 8 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools19Not listed

Tools & capabilities

Slack MCP Server tools 19

  • slack_token_statusCheck token health, age, auto-refresh status, and cache stats
  • slack_health_checkCheck if Slack tokens are valid and show authentication status
  • slack_refresh_tokensForce refresh tokens by extracting from Chrome (requires Slack tab open in Chrome)
  • slack_list_conversationsList all DMs and channels with user names resolved. Uses cached DMs by default for speed.
  • slack_conversations_historyGet messages from a channel or DM with user names resolved
  • slack_get_full_conversationExport FULL conversation history with all messages, threads, and user names. Can save to file.
  • slack_search_messagesSearch messages across the Slack workspace
  • slack_users_infoGet detailed information about a Slack user
  • slack_send_messageSend a message to a channel or DM
  • slack_get_threadGet all replies in a message thread
  • slack_list_usersList all users in the workspace
  • slack_add_reactionAdd an emoji reaction to a message
  • +7 more on the listing page

Vexa tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Slack MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "jtalk22-slack-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jtalk22/slack-mcp"
      ]
    }
  }
}

Vexa

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vexa": {
      "url": "https://api.cloud.vexa.ai/bots"
    }
  }
}

Frequently asked questions

Slack MCP Server is categorized under Communication and uses a local stdio subprocess. Vexa belongs to Communication and uses a remote HTTP/SSE transport. Pick Slack MCP Server for communication work and Vexa for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Slack MCP Server is listed as freemium — a free tier with paid plans. Auth: other. Vexa has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add jtalk22-slack-mcp-server and vexa as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Slack MCP Server has a quality signal of 68/100 (Great) with 8 views, 0 installs and 32 GitHub stars. Vexa has 48/100 (Fair) with 2 views, 0 installs and 2,905 GitHub stars.