Skip to main content
Glama
project-nomos

nomos-slack-mcp

by project-nomos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nomos-slack-mcp

No user-submitted related servers found.

    Related Servers

    • cyber-slack

      cyberuni
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Slack that enables AI agents to interact with Slack workspaces, including listing channels, reading and posting messages, searching, managing users, reactions, and user groups.
      1
      MIT

    • Slack MCP Server

      rokej
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI agents to send messages, payloads, and Markdown-formatted content to Slack via Incoming Webhooks.
      3
      Apache 2.0

    • slacker

      manasnilorout
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents such as Claude Code to read and send Slack messages as the user through a local MCP server, supporting multiple workspaces, threads, search, reactions, statuses, and dry-run/read-only safeguards.
      13
      MIT

    • slack-mcp

      EgumaYuto
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with Slack using a user token. It allows reading channels, DMs, threads, search, and posting messages as the authenticated user.
      15 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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Slack operation: listing, reading, sending, replying, searching, status, and reactions. There is no meaningful overlap between tools; even read_messages and read_thread are clearly separated by message stream vs. thread replies.

    Naming Consistency4/5

    All tools follow the slack_ prefix with snake_case and mostly use a verb_noun pattern like slack_list_channels and slack_send_message. The only minor deviation is slack_search, which omits an explicit object, but it remains clear and consistent in style.

    Tool Count5/5

    Ten tools is well-scoped for a Slack integration server. Each tool covers a distinct common Slack action without unnecessary redundancy or bloat.

    Completeness4/5

    The toolset covers the core Slack workflows: reading, sending, replying, searching, listing users/channels/workspaces, setting status, and reacting. Minor gaps like file uploads, channel creation, or message deletion exist but do not break typical assistant use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources