Skip to main content
Glama
epdlr

slack-stdio-mcp

by epdlr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to slack-stdio-mcp

No user-submitted related servers found.

    Related Servers

    • slack-mcp-claude-auth

      kamilmodest
      F
      license
      Not graded
      quality
      D
      maintenance
      Local stdio MCP proxy for the official Slack MCP endpoint, using Claude's Slack plugin for authentication to enable Slack integration via MCP without needing a custom Slack app.
      -

    • claude-slack-channel

      elys0912
      A
      license
      Not graded
      quality
      B
      maintenance
      Relays Slack direct messages into a locally running Claude Code session over MCP, so users can talk to their local agent from Slack. Replies, reactions, and execution-permission approvals (buttons or yes/no replies) are all handled inside Slack without opening ports or tunnels.
      5 npm
      MIT

    • 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

    • mcp-remote

      abluva
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.
      19 npm
      54
      MIT

    • Slack MCP

      korotovsky
      A
      license
      B
      quality
      D
      maintenance
      The most powerful MCP server for Slack Workspaces. This integration supports both Stdio and SSE transports, proxy settings and does not require any permissions or bots being created or approved by Workspace admins 😏.
      2
      1,854
      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.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct capability: auth initiation, auth status, file download, catalog inspection, message update/delete, reaction removal, and scheduled message list/cancel. Even the two auth-related tools are clearly separated into start-flow versus status-report roles, so an agent should not confuse them.

    Naming Consistency4/5

    All tools share the consistent slack_stdio_ prefix and use lowercase snake_case, which makes the set predictable. However, not every name follows verb_noun: reauth, catalog, session_status, and scheduled_messages are deviations, though they remain readable and still fit the overall pattern.

    Tool Count5/5

    Eight tools is a well-scoped size for a Slack MCP bridge that supplements a hosted catalog with missing operations. Every tool addresses a concrete gap or supporting need, with no redundant clutter.

    Completeness5/5

    The tool surface covers the stated gaps: reauthorization, file downloads, message editing/deletion, reaction removal, and scheduled message list/cancel. It also includes status and catalog tools to make the bridge self-explanatory, so there are no obvious dead ends for the server's intended role.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources