Skip to main content
Glama
tomfunk

slack-readonly-mcp

by tomfunk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to slack-readonly-mcp

No user-submitted related servers found.

    Related Servers

    • slack-read-mcp

      zio3
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for Slack that reads messages from channels the bot is invited to, without storing data. It provides tools to fetch channel history, thread replies, and resolve user IDs, with access controlled solely by channel invitations.
      MIT

    • slack-mcp

      duolingo
      A
      license
      Not graded
      quality
      B
      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

      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.
      17,928 npm
      3
      MIT

    • 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

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

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing vs single item, history vs search, threads vs general messages, users vs user info. No overlap.

    Naming Consistency5/5

    All tools follow the consistent 'slack_verb_noun' pattern (e.g., slack_list_channels, slack_user_info). Minor variation between 'channel_history' and 'conversations_info' but both are noun phrases in the same style.

    Tool Count5/5

    7 tools is well-scoped for a read-only Slack server, covering channel exploration, history, threads, user info, and search without being excessive.

    Completeness4/5

    Covers core read operations (channel list, history, threads, users, search). Minor gaps like reading pinned messages or files, but these are less critical for a read-only interface.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources