Skip to main content
Glama
korotovsky

Slack MCP

by korotovsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to Slack MCP

No user-submitted related servers found.

    Related Servers

    • Slack MCP Server

      Themetralla3000
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Slack workspace integration. This server allows AI assistants to interact directly with your Slack workspace, providing tools to manage channels, send messages, list users, and upload files.
      30,839 npm
      1
      MIT

    • Slack Notify MCP

      SilasReinagel
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for posting messages to Slack channels via webhooks or bot API. Supports configurable usernames, emojis, and both webhook and bot token authentication modes.
      4 npm
      MIT

    • mcp-slack

      gregbuehler
      A
      license
      A
      quality
      C
      maintenance
      MCP server that reads Slack through your own browser session, authenticating as you rather than a bot. Provides tools to search messages, retrieve channel/DM/thread history, resolve users, and post messages (write disabled by default).
      10
      MIT

    • Slack MCP Server

      kamolc4
      A
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.
      30,839 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

    B3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: channels_list retrieves a list of channels, while conversations_history fetches messages from a specific channel. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency4/5

    Both tools follow a consistent snake_case naming convention, but the patterns differ slightly: channels_list uses a noun_verb format, while conversations_history uses a noun_noun format. This minor deviation prevents a perfect score, but the naming is still readable and mostly consistent.

    Tool Count2/5

    With only 2 tools, this server feels too thin for a Slack integration, as it lacks essential operations like sending messages, managing users, or updating channel settings. The scope is severely limited, making it difficult for agents to perform comprehensive Slack-related tasks.

    Completeness2/5

    The tool surface is significantly incomplete for a Slack domain. While it covers listing channels and retrieving message history, it misses critical operations such as posting messages, creating channels, or handling reactions, which are core to Slack workflows and will likely cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources