Skip to main content
Glama
oregpt

Slack MCP Server

by oregpt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Slack MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

      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
      14 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

      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-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
      -
    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

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: channels_list lists channels, conversations_add_message posts messages, conversations_history retrieves channel history, and conversations_replies fetches thread replies. There is no overlap in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency4/5

    The tool names follow a consistent snake_case pattern and use descriptive verbs like 'list', 'add', and 'history'. However, 'channels_list' deviates slightly from the 'conversations_' prefix used by the other three tools, which is a minor inconsistency.

    Tool Count3/5

    With only 4 tools, the server feels thin for a Slack integration, as it lacks common operations like updating or deleting messages, managing users, or handling reactions. While the tools cover basic messaging and channel listing, the scope is limited, potentially requiring workarounds for full Slack workflows.

    Completeness2/5

    The tool set is significantly incomplete for a Slack server. It covers listing channels and basic message operations (posting, retrieving history, and thread replies), but misses essential CRUD actions like editing or deleting messages, user management, file handling, and event subscriptions. This will likely cause agent failures in more complex interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources