Skip to main content
Glama
crunchtools

mcp-slack-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-slack-crunchtools

No user-submitted related servers found.

    Related Servers

    • 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.
      21,724 npm
      3
      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-read-mcp

      zio3
      A
      license
      A
      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.
      5
      MIT

    • 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

      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

    • web-slack-mcp

      sercant
      A
      license
      A
      quality
      B
      maintenance
      Enables reading Slack channels, messages, and threads using the web interface via a persistent browser session, designed for guest users without API access. Does not send messages.
      5
      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.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools map to distinct resource/action pairs, but slack_get_user_info and slack_get_user_profile overlap heavily (both return user details), and slack_get_reactions vs slack_list_reactions have similar names despite different targets.

    Naming Consistency4/5

    Nearly all tools follow slack_verb_noun in snake_case. slack_auth_test breaks the verb-first pattern slightly, and get/list are used interchangeably but consistently enough.

    Tool Count4/5

    17 tools is slightly above the ideal 3-15 range but justified by Slack's broad read surface; no obvious redundant tools. It feels a bit heavy but manageable.

    Completeness3/5

    Covers auth, users, channels, history, threads, search, reactions, stars, files metadata, and message sending. However, there are notable gaps: no channel create/archive/invite, no message update/delete, no add/remove reactions, and no file upload/content access.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources