Skip to main content
Glama
Sign In
mcp_slack

mcp_slack

by Abu-BakarYasir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp_slack

No user-submitted related servers found.

    Related Servers

    • agenthub MCP

      thebusted
      A
      license
      Not graded
      quality
      D
      maintenance
      A bearer-authed message hub for AI coding agents to communicate across machines and sessions, providing tools for sending, polling, and managing channels.
      MIT

    • Agent Lounge MCP Server

      lurkwizard
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read and post messages in a public chat room through a stateless Streamable HTTP JSON-RPC endpoint with tools for structured bot-to-bot messaging, threads, public DMs, tasks, and polls.
      20 npm
      MIT

    • kintio

      Gkxie
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables connecting chat channels to an Agent you control, letting authorized people assign work, steer ongoing tasks, and receive results directly from their chat app.
      9 npm
      Apache 2.0

    • Ping

      r0wh4n
      A
      license
      Not graded
      quality
      B
      maintenance
      Connect AI agents to shared Ping chat rooms for collaboration, with auto-delivery of new messages. Enables agents to chat and share context with each other through the MCP protocol.
      239,977 npm
      1
      MIT

    • claudechat

      zzibo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code agents to communicate across sessions, terminals, and repositories through shared channels with persistent context.
      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.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct, but get_recent_slack_messages and get_user_messages could be confused as both fetch messages from channels. However, get_user_messages specifies a user filter, which helps differentiate it. The other tools (get_user_info, post_message) have clear, non-overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_recent_slack_messages, post_message). There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count3/5

    With only 4 tools, the server feels thin for a Slack integration, which typically involves more operations like managing channels, files, or reactions. However, it covers basic messaging and user info, so it's borderline but not severely lacking.

    Completeness3/5

    The server covers core messaging operations (post and fetch) and user info, but there are notable gaps such as updating or deleting messages, listing channels, or handling reactions. Agents can work around this for basic tasks, but advanced workflows may fail.

    Resources