Skip to main content
Glama
oviron

slack-personal-mcp

by oviron

Related Servers

Alternatives to slack-personal-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Slack using a user token, providing full access to message search, channel history, DMs, and posting as the user.
      8
      -
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants like Cursor and Claude Desktop to interact with Slack workspaces, allowing message sending, channel reading, user management, and file operations through natural language.
      MIT
    • 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

    TDQS

    B3.4/5.0

    Scored across 30 tools

    Disambiguation3/5

    Most tools target a distinct resource+action, but slack_search and slack_search_messages are genuinely confusable: both search messages, one via RTS with cursors and one via raw query with filters, and an agent can easily pick the wrong one. A few others (slack_unread vs slack_read_channel, slack_lint vs the style gate inside slack_send_message) require reading descriptions carefully to separate.

    Naming Consistency4/5

    The dominant pattern is slack_verb_noun (send_message, edit_message, list_files, add_reaction), which is predictable once learned. Minor deviations exist: bare-verb slack_search, and noun-only names like slack_user_info, slack_channel_info, slack_file_info, and slack_unread break the verb-first convention, while verbs vary between get/read/find for similar lookups.

    Tool Count3/5

    30 tools is on the heavy side for a personal Slack client, and the surface spans many sub-domains (messages, files, channels, users, reactions, scheduling, status, canvases, emoji, usergroups). Each tool covers real functionality, but the count is borderline and a few could be folded together.

    Completeness4/5

    Message lifecycle is well covered (send, edit, delete, schedule, cancel, reactions, thread reading, permalink), along with files, users, and info lookups. Gaps remain: there is no tool to list the channels/conversations you belong to (slack_find_channel requires a name, and slack_unread requires naming channels), and no pin/bookmark or channel create/join operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues