Skip to main content
Glama
zio3

slack-read-mcp

by zio3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to slack-read-mcp

No user-submitted related servers found.

    Related Servers

    • slack-readonly-mcp

      tomfunk
      A
      license
      A
      quality
      D
      maintenance
      A self-hosted, read-only Slack MCP server that runs locally and provides read-only access to Slack channels, messages, and users via the Slack Web API, with no third-party intermediary.
      7
      MIT

    • Slack MCP Server

      mynghn
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to access Slack workspace data, including channels, messages, threads, and user information.
      30,329 npm
      3
      MIT

    • slack-mcp

      duolingo
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Slack with OAuth 2.1 authentication, enabling message retrieval, thread replies, search, user and channel listing.
      9
      Apache 2.0

    • Slack MCP Server

      aryahadii
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Slack data including messages, channels, and users through secure API endpoints.
      MIT

    • Slack MCP Server

      kamolc4
      A
      license
      Not graded
      quality
      C
      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,329 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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    get_channel_history and get_thread_replies are explicitly separated by thread inclusion, while list_active_threads is a polling summary tool that points to where to read next. list_channels and resolve_user operate on clearly different resources, so no two tools are likely to be confused.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get for direct reads, list for enumeration, and resolve for user lookup. The naming is uniform and predictable across the entire set.

    Tool Count5/5

    Five tools is a compact and appropriate surface for a read-only Slack integration. Each tool provides a distinct read operation with no unnecessary duplication or bloat.

    Completeness4/5

    The core read workflows are covered: channel enumeration, message history, thread replies, active-thread polling, and user ID resolution. Minor gaps such as listing all users or fetching a single message by ID prevent a perfect score but do not block typical use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources