Skip to main content
Glama
farsght

slack-user-mcp-server

by farsght
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to slack-user-mcp-server

No user-submitted related servers found.

    Related Servers

    • slack-mcp

      asaphe
      A
      license
      B
      quality
      B
      maintenance
      Enables an AI assistant to act as the user in Slack through a user OAuth token, covering messaging and threads, search, users, channels, user groups and reactions, plus scheduled messages, canvases and Slack Lists. It also supports flexible channel addressing by ID, #name or @user, and matches existing tool names and parameters for seamless integration with established prompts and permission rules.
      22
      MIT

    • slack-bot-mcp

      LiusDev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate in Slack as a bot, sending direct and channel messages, finding members, reading history and threads, adding reactions, and waiting for or checking replies.
      14
      1,624 npm
      MIT

    • slack-mcp-server

      dudztroyer
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Slack workspaces, including listing channels, posting messages, replying to threads, adding reactions, and retrieving user information.
      10
      18 npm
      MIT

    • Slack MCP Server

      oregpt
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to interact with Slack workspaces through OAuth authentication, supporting message reading, posting to channels and threads, and channel discovery with popularity sorting.
      4
      MIT

    • Slack User MCP Server

      lars-hagen
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Slack workspaces as a user, supporting channel listing, message posting, threading, reactions, and user management via the Slack API.
      8
      11
      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 8 tools

    Disambiguation5/5

    Each tool targets a distinct Slack operation: searching messages, listing channels, fetching channel history, posting messages, looking up users, getting user details, testing auth, and fetching thread replies. There is no overlap that would confuse an agent.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'slack_<verb>_<noun>', with clear verbs like search, list, get, post, lookup, and auth_test. This provides a predictable and readable naming convention.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose. It covers the essential Slack operations without unnecessary bloat or missing critical functions.

    Completeness4/5

    The tool set covers core workflows: searching, reading history, posting messages, handling threads, and user operations. Minor gaps exist, such as message editing/deleting or adding reactions, but these are not critical for typical Slack automation and can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources