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.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool has a distinct action and target resource: threads, reactions, unread counts, user search, message sending, token management, workflow profiles, and conversation history all occupy clear boundaries. Even overlapping areas like token_status, health_check, and refresh_tokens address different facets (status vs. refresh). No two tools appear to do the same thing.

    Naming Consistency4/5

    All tools follow a consistent `slack_` prefix and snake_case naming. Most use an intuitive verb_noun order (get_thread, add_reaction, send_message), though a few like `slack_conversations_mark` and `slack_conversations_unreads` invert to noun_verb. Overall the pattern is predictable and easy to scan, with only minor deviations.

    Tool Count4/5

    At 19 tools, the surface is slightly larger than the typical 3–15 sweet spot, but the breadth is justified given the domain spans messaging, reactions, search, user administration, token management, and a custom workflow system. No tools feel redundant, though a few (e.g., `slack_users_info` vs. `slack_users_search`) overlap slightly in purpose. The count is on the high side but still well-scoped.

    Completeness4/5

    The toolset covers core lifecycle actions for messages, threads, reactions, and users, plus advanced features like workflow profiles and full conversation exports. Obvious gaps include editing/deleting messages, creating or leaving channels, and pinning content, but these are minor and agents can work around them. The inclusion of token management and workflow automation makes the surface feel complete for its intended use case.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources