Skip to main content
Glama
Hais

Slack MCP Server

by Hais
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Slack MCP Server

No user-submitted related servers found.

    Related Servers

    • Slack MCP Server

      bcharleson
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Slack workspaces through comprehensive channel management, messaging, direct messages, search functionality, and user management capabilities.
      30
      6 npm
      2
      MIT

    • Slack MCP Server

      ampcome-mcps
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Slack workspaces through natural language, supporting channel management, message operations, user profiles, reactions, and threaded conversations.
      -

    • Slack MCP Server

      lbeatu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Slack workspaces through comprehensive integration capabilities. Supports channel management, messaging, thread replies, reactions, and message history retrieval through natural language commands.
      56 npm
      MIT

    • 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

    • slack-mcp-server

      dudztroyer
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Slack workspaces, including listing channels, posting messages, replying to threads, adding reactions, and retrieving user information.
      10
      11 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 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions, such as send_message vs. send_formatted_message for different message types, and add_reaction vs. remove_reaction for opposite operations. There is no significant overlap that would cause confusion in tool selection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with clear, descriptive actions like create_channel, get_channel_history, and update_message. The naming is uniform throughout, using snake_case without any deviations or mixed conventions.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for a Slack integration covering channels, messages, users, files, and reactions. It provides comprehensive functionality without being overwhelming, though it borders on the upper limit of typical scopes.

    Completeness5/5

    The toolset offers complete CRUD/lifecycle coverage for Slack's core domain, including channel management (create, archive, invite, list, get info), message handling (send, update, delete, search, history), user operations (list, get info), and file uploads. No obvious gaps exist for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources