原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

SockDock for Slack

作者:iwamatsu0430版本 0.2.1i★ 0i在你的电脑上运行官方网站 ↗
注册名称io.github.iwamatsu0430/sockdock

安装方法

能做什么

Manage SockDock rules: Slack posts that run Claude Code, Codex or a program on your Mac.

作者提供的原文

  • 连接方式 在你的电脑上运行
  • 账号或密钥 无需密钥
  • 分类 聊天与邮件

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 SockDock for Slack 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 SockDock for Slack,或回答中出现 SockDock for Slack 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 SockDock for Slack

SockDock for Slack 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 SockDock for Slack 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 SockDock for Slack

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 SockDock for Slack 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 SockDock for Slack

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 SockDock for Slack 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 SockDock for Slack

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 SockDock for Slack 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 SockDock for Slack 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.2.1
发布到注册中心i
2026年11月17日
代码最后更新i
2026年11月19日
作者
iwamatsu0430
软件包
mcpb: …/SockDock-0.2.1.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 iwamatsu0430 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/iwamatsu0430-sockdock.svg)](https://mcp.popnx.com/en/servers/iwamatsu0430-sockdock)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 2038 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2038 个服务器的 90% 更新
  • 基础检查结果等于或优于此分类中其他 2038 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

SockDock for Slack 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.2.1)于3天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost广泛使用↓ 5432/周★ 13956天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

作者:w1ne起步阶段★ 3524天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
SockDock for Slack
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置需要安装在电脑上云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查3/35/54/44/44/44/4
许可证MITMITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

SockDock for Slack

Run Slack apps locally: one Socket Mode connection, many handlers.

Website · 日本語

SockDock (sockdock) is a small gateway that runs on your Mac. It receives messages from your Slack workspace over Socket Mode — nothing needs to be reachable from the internet — and hands them to handlers you configure:

  • command handlers: any program. It gets the message as JSON on stdin; its stdout is posted back to the thread.
  • claude handlers: Claude Code in headless mode. Each Slack thread is one conversation that continues on every reply, limited to the tools you allow.
  • codex handlers: Codex CLI in headless mode, the same way. Web search and file edits follow the rule; commands always run in Codex's sandbox.

Think of it as a power strip: Slack apps allow one socket, and SockDock lets you plug many things into it. A top-level message that matches a route (a channel, or DMs to the app, plus a condition) starts a thread; every reply in that thread goes to the same handler.

It comes with a CLI and an optional menu bar app.

SockDock is not affiliated with, created by, or supported by Slack Technologies, LLC.

Status: early development. macOS 13+ is the main target (the CLI also works on Linux).

Quick start

1. Install

With Homebrew:

brew install --cask iwamatsu0430/tap/sockdock   # menu bar app

brew install --formula iwamatsu0430/tap/sockdock # CLI (macOS, Linux)

The app is not notarized by Apple, so the first time you open it, macOS stops it with “SockDock” Not Opened:

  1. Click Done (not Move to Trash).
  2. Open System Settings → Privacy & Security, scroll down and click Open Anyway.
  3. When asked again, click Open. From then on it opens normally.

This allows SockDock only; the rest of your Mac's protection stays on. Homebrew checks the download against the checksum recorded in the tap before installing it. See also Safely open apps on your Mac.

Or build from source. Tools are managed with mise.

git clone https://github.com/iwamatsu0430/sock-dock-slack.git

cd sock-dock-slack mise install # Go, Node, wails3 mise run build # -> bin/sockdock mise run app # optional: -> dist/SockDock.app (menu bar app, CLI bundled)

If you built it, put bin/sockdock somewhere on your PATH (the examples below assume sockdock is on it).

2. Create the Slack app
sockdock manifest
  1. Open https://api.slack.com/apps?new_app=1, choose From a manifest, and paste the manifest.
  2. Basic Information → App-Level Tokens: generate a token with the connections:write scope (xapp-…).
  3. Install App: install it to your workspace and copy the Bot User OAuth Token (xoxb-…).
  4. Invite the bot to every channel you want to route from: /invite @SockDock. DMs to the app need no invite.

Optional: to show SockDock's icon on its replies, upload assets/slack-icon.png as the app icon (Basic Information → Display Information). Slack manifests can't set it.

3. Store the tokens
sockdock auth set     # prompts for both tokens and stores them in the macOS Keychain

sockdock auth status

Alternatively, export SLACK_APP_TOKEN and SLACK_BOT_TOKEN, or point settings.secrets_file at a chmod 600 .env file.

4. Configure routes
sockdock init         # writes a starter config with an "echo" route

mkdir -p ~/sockdock-handlers cp examples/echo.sh ~/sockdock-handlers/ # the handler that route runs

Edit the config and replace C0123456789 with your channel's ID.

The config lives at ~/Library/Application Support/sockdock/config.yaml (Linux: $XDG_CONFIG_HOME/sockdock/config.yaml). A minimal route:

routes:
  • name: echo channel: C0123456789 # channel ID (channel details → bottom of the About tab) starts_with: echo # posts that start with "echo" handler: type: command cwd: ~/sockdock-handlers command: ["./echo.sh"]

A route reacts to top-level posts that meet one of these conditions. Within a channel, routes are tried from the top and the first match runs (routes that are off are skipped).

KeyPosts it runs ongroups
starts_with: echoPosts starting with the keywordtext: what follows the keyword
contains: reviewPosts containing the keywordtext: the whole post
match: '^deploy (?P \w+)$'Posts matching the regular expression (RE2)the named groups
all_posts: trueEvery posttext: the whole post

Keywords ignore case, full-width vs half-width characters, repeated spaces and a leading mention of the Slack app. A keyword of letters and digits does not match inside a word (entry does not match entryx). Regular expressions are case sensitive. Add mention_only: true to run a route only for posts that mention the Slack app, and use channel: dm for DMs (see "DMs and mentions" below).

Check it:

sockdock check

sockdock match C0123456789 "echo hello"

5. Run
sockdock run                # in the foreground (Ctrl-C to stop)

sockdock service install # or, without the menu bar app: start at login, restart on failure (launchd / systemd) sockdock status

Post echo hello in the channel: SockDock reacts with 👀, runs the handler and replies in the thread.

Or use the menu bar app

With the app you do not need steps 3–5 above or any YAML. Open SockDock from Applications (built from source: open dist/SockDock.app or mise run gui):

  1. Setup (first launch): *Open api.slack.com* opens Slack's "create an app" page with the manifest filled in. Install the app, generate an App-Level Token with connections:write, then paste both tokens and press Connect to Slack. The tokens are checked with Slack first and saved to the Keychain only if both work. To use a Slack app you already have, open Use a Slack app you already have in setup: it lists the settings (Socket Mode, the message.channels/message.groups events, Bot Token scopes, for DMs the optional message.im event, im:history scope and Messages tab, and for attached files the optional files:read scope) and copies the part to add to its App Manifest. With Socket Mode on, that app's events go only to SockDock. If required scopes are missing, Connect to Slack names them.
  2. Rules → Add Rule: pick the channel (channels the Slack app has been added to are listed; without the channels:read/groups:read scopes, enter a channel ID or link) or DM, choose who can run it (everyone in the channel, or people you choose by name), choose which posts it reacts to (starting with, containing, a regular expression, or all; tick *Only when mentioned* to need a mention of the Slack app), and choose what runs — an AI agent (Claude Code or Codex) in a working folder, with instructions and what it may do, or a program. The list is grouped by channel and shows each rule's last run. Within a channel the rule higher up comes first; drag ⠿ to reorder. Open a rule for recent runs, thread links and Stop.
  3. Post something like … in the channel.

The app runs the gateway while it is open — there is no separate service to install. Clicking the menu bar icon shows the connection, running and recent runs; There is one window: switch between Rules and Settings at the top. Settings (⌘,) has the Slack connection and who you are in Slack (see "Notifications by DM"), *Open at login*, notifications (Mac and Slack DM), the language (also used for the messages posted to Slack), MCP and Reset SockDock…, which removes the tokens, rules, run history and app settings and starts over from setup (the config file goes to the Trash; logs are kept). Open Config File opens the YAML in your editor for anything the form does not cover. A rule with a problem (e.g. a missing folder, or a rule above that always matches first) is shown in red and left out; the other rules keep running.

If a sockdock service install service is already running, the app shows its state and does not start its own gateway.

Who can run a rule

Anyone who can post in a channel can trigger its rules. To limit a rule to some people, list their Slack member IDs:

routes:
  • name: deploy channel: C0123456789 starts_with: deploy allowed_users: [U0123ABCD, U0456EFGH] handler: { type: command, cwd: ~/ops, command: ./deploy.sh }
  • Posts and thread replies from anyone else are ignored: no 👀, no reply, and they never reach the handler. A rule further down the channel can still pick up their post.
  • In the app, open the rule, set Who Can Run It to Chosen People and add people by name. Choosing by name needs the users:read scope, which the bundled manifest includes. Without it, enter member IDs (in Slack, a profile's ⋮ menu → Copy member ID). users:read lets the app read the profiles of the workspace's members; SockDock uses it only for this list.
  • An agent rule that is open to everyone and may run commands or edit files shows a warning in the app.

Handlers

Every handler receives this JSON (on stdin for command handlers):

{

"route": "echo", "turn": 1, "channel": "C0123456789", "thread_ts": "1762920000.000100", "permalink": "https://example.slack.com/archives/C0123456789/p1762920000000100", "groups": { "text": "hello" }, "messages": [{ "ts": "1762920000.000100", "user": "U0123", "text": "echo hello" }] }

groups holds the values taken from the first message (see the table above) and is passed on every turn of the thread.

Attached files

Files attached to a post or a thread reply (screenshots, logs, PDFs, …) are handed over with it, so you can ask "look at this screenshot". A message with files gets a files list:

"messages": [{ "ts": "1762920000.000100", "user": "U0123", "text": "check this log",

"files": [ { "name": "app.log", "mimetype": "text/plain", "size": 18233, "path": "/Users/me/Library/Caches/sockdock/files/812/app.log" }, { "name": "build.zip", "mimetype": "application/zip", "size": 73400320, "skipped": "too_large" } ] }]

  • The files are saved for this run only (in ~/Library/Caches/sockdock/files/, outside the rule's folder) and deleted when it ends. Copy them if you need them later.
  • A file that is not handed over has skipped instead of path: too_large (over settings.max_file_mb, 20 MB by default), external (stored outside Slack, e.g. Google Drive), unsupported (Slack posts and canvases), no_scope (the Slack app lacks files:read) or failed. The run goes ahead with the text and the other files; SockDock posts nothing about it, so the handler decides whether to mention it.
  • Only files of posts that start or continue a run are fetched. Posts from people a rule does not allow are never fetched.
  • This needs the files:read Bot Token scope, which the bundled manifest includes. Without it, the rule's recent runs say the files were not passed on. files:read can read files in the channels and DMs the Slack app is in; SockDock reads only the files of posts that run a rule.
  • File contents are untrusted input, just like the post text: a screenshot or a log can contain instructions aimed at the agent.
command
handler:

type: command cwd:

只显示了开头部分;其余内容请在仓库中阅读