Skip to main content
Glama
Sign In
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.
      49,032 npm
      3
      MIT

    • slack-mcp

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

    • discord-context-bridge

      wouthh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables authorized MCP clients to perform five read-only operations — checking connection status, listing conversations, reading messages, searching, and polling for changes — over selected Discord server channels and DMs, with scope-based authentication, retention limits, and no ability to send messages or moderate.
      1
      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.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (channel history vs. thread replies vs. search vs. members). The weakest pair is slack_get_user_info vs. slack_get_user_profile, which read as near-duplicates, and get_reactions vs. list_reactions require reading descriptions carefully to separate (reactions on a message vs. reactions by a user). Otherwise selection is straightforward.

    Naming Consistency5/5

    Every tool uses the same slack_ prefix followed by a verb_noun pattern (get_channel_info, list_users, send_message, cancel_scheduled_message). There are no camelCase or stylistic deviations, and the verbs (get/list/search/send/cancel/test) map predictably to the operation type.

    Tool Count4/5

    Seventeen tools is slightly above the ideal band but is well justified for a Slack surface spanning users, channels, messages, threads, reactions, stars, and files. Each tool covers a distinct Slack endpoint rather than being redundant padding.

    Completeness3/5

    The surface is heavily read-oriented: there is no add_reaction, no update/edit message, no delete message, no channel create/join/leave, and no file upload (files are explicitly metadata-only). Sending, scheduling, and cancelling messages are covered, but an agent asked to react to, edit, or upload would hit dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources