Skip to main content
Glama
Strand-AI

Slack Notifier MCP

by Strand-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Slack Notifier MCP

No user-submitted related servers found.

    Related Servers

    • Slack Note Capture MCP Server

      larrygmaguire-hash
      F
      license
      A
      quality
      Not graded
      maintenance
      Enables two-way communication between Claude and Slack for posting messages, managing threads, and handling files. It specifically supports asynchronous workflows by allowing Claude to poll for remote user replies and send task notifications.
      9
      -

    • AskOnSlackMCP

      trtd56
      F
      license
      Not graded
      quality
      D
      maintenance
      A Human-in-the-Loop MCP server that enables AI assistants to request information or clarification from humans via Slack. It uses real-time, thread-based conversations with socket mode integration to bridge the gap between AI systems and human experts.
      6
      -

    • 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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: ask_user for interactive questions, get_thread_replies for retrieving thread responses, and send for posting messages. No semantic overlap.

    Naming Consistency4/5

    All tools use snake_case verb_noun pattern (ask_user, get_thread_replies), with 'send' being a single-verb exception but still follows the verb-first convention. Minor inconsistency in specificity.

    Tool Count3/5

    Three tools is minimal for a Slack integration, but the server's 'notifier' scope justifies a lean set. Still, the surface feels thin compared to typical Slack API needs.

    Completeness3/5

    Core messaging workflows are covered: send, read replies, and ask for input. However, missing essential operations like listing channels, updating messages, or managing reactions limit the surface.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources