Skip to main content
Glama
jtalk22

Slack MCP Server

by jtalk22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Slack MCP Server

No user-submitted related servers found.

    Related Servers

    • slack-user-mcp-server

      farsght
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Slack using a user token, providing full access to message search, channel history, DMs, and posting as the user.
      8
      -

    • easy-slack-mcp

      easynet-world
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Cursor and Claude Desktop to interact with Slack workspaces, allowing message sending, channel reading, user management, and file operations through natural language.
      -

    • Slack MCP Server

      cnye36
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Slack workspaces through secure OAuth 2.0 authentication. Supports posting messages, reading channel history, and listing channels across multiple workspaces with production-ready security features.
      -

    • Slack MCP Server

      iskifogl
      A
      license
      A
      quality
      D
      maintenance
      Integrates AI assistants with Slack workspaces using OAuth 2.0 authenticated user tokens for secure, multi-functional interaction. It enables comprehensive operations including channel management, message searching, file handling, and reaction management through natural language.
      20
      169 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct Slack resources and actions, but slack_health_check, slack_token_status, and slack_refresh_tokens form an overlapping token-management cluster, and slack_conversations_history vs slack_get_full_conversation can be confused. Descriptions largely disambiguate, so an agent can usually choose correctly.

    Naming Consistency4/5

    All tools use the slack_ prefix and snake_case, which is highly predictable, but internal ordering alternates between verb_noun (list_conversations, send_message) and noun_verb (users_info, conversations_history). This mirrors Slack's API inconsistently but remains readable.

    Tool Count3/5

    20 tools is in the heavy range for an MCP server, and some peripheral clusters (token management, workflow profiles, session reporting) could potentially be consolidated. However, Slack is a broad domain, so most tools earn their place.

    Completeness4/5

    Core Slack workflows are covered: reading, sending, searching, threads, reactions, user lookup, and conversation management. Gaps exist for editing/deleting messages, file uploads, and channel administration, but agents can work around these for the server's monitoring and catch-up focus.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources