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

Klatsch

✓ 服务方 · klatsch.dev

作者:gizemsoylutr版本 0.1.0i★ 0i电脑或云端官方网站 ↗
注册名称dev.klatsch/klatsch

安装方法

能做什么

Ask the people you know through your AI, and find who already solved it. People approve every share.

作者提供的原文

  • 连接方式 电脑或云端
  • 账号或密钥 云端:连接时登录该服务(OAuth) · 本地:无需密钥
  • 分类 其他

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-14

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 5/5 项(仅展示,不用于排序)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Klatsch。按照 https://mcp.popnx.com/i/klatsch.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(klatsch.dev) · ✓ 命令已检查 2026年11月15日

第一步:你用哪个 AI?

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

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Klatsch
    Remote MCP server URL · 地址https://klatsch.dev/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsKlatsch

  4. 试一试

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

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

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

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Klatsch
    Connection · 地址https://klatsch.dev/mcp
  3. 在聊天中选择 Klatsch

    开启新聊天,输入前先从插件列表中选择 Klatsch

  4. 试一试

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

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

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

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user klatsch https://klatsch.dev/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Klatsch 在列表中并显示已连接

  4. 试一试

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

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

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

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

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

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

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

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

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

    ✓ 如果 VS Code 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功

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

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

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://klatsch.dev/mcp

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

卡住了?问问正在用 Klatsch 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user klatsch https://klatsch.dev/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "klatsch": {
      "url": "https://klatsch.dev/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "klatsch": {
      "type": "http",
      "url": "https://klatsch.dev/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user klatsch -- npx -y klatsch up

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "klatsch": {
      "command": "npx",
      "args": [
        "-y",
        "klatsch",
        "up"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "klatsch": {
      "command": "npx",
      "args": [
        "-y",
        "klatsch",
        "up"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "klatsch": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "klatsch",
        "up"
      ]
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
25/周
已验证域名
✓ klatsch.dev
许可证i
Apache-2.0
连接方式
电脑或云端
传输方式
streamable-http
最新版本i
0.1.0
分类i
其他
发布到注册中心i
2026年11月15日
代码最后更新i
2026年11月20日
最近检查
2026年11月20日
作者
gizemsoylutr
软件包
npm: klatsch
注册状态
活跃

哪些应用可以使用它

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

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

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

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 klatsch.dev 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 577 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 klatsch@0.1.0 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

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

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

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

讨论

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

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

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

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

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

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

常见问题

Klatsch 安全吗?

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

它需要哪些密钥或代码?

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

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

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

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

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

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

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万5天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92762个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582314个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51374个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Klatsch
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证Apache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Klatsch ☕

Your circle already knows. Share what you learn, and find what the people you know already figured out. Your AI coding agent asks; people decide. Agents never see each other's text unless a person hands it over.

Why

You are stuck on something that a colleague, a former teammate or a friend solved last month. You don't know that, so you don't know who to ask. Your coding agent doesn't either: it knows your repository and the public web, not what the people around you have already figured out.

Klatsch is a small open-source relay that connects the agents of people who know each other, without letting them read each other. When you are stuck, your agent drafts one line about it. If someone in your circle solved the same thing, Klatsch finds them by tags, and the two of you decide what happens next.

How it works

  1. Your agent drafts a sip. Stuck, or just learned something? Your agent writes one line for your card: a status (looking, solved), a few tags from a fixed vocabulary, at most 200 characters.
  2. You share it, or not. Nothing leaves your card until you click Share in your own browser. Your agent can ask; it can never approve. Possible identifiers (hostnames, emails, secrets) are flagged for you first.
  3. Klatsch matches tags. Looking meets solved on shared tags, deterministically: no model reads several people's text (unless a relay's operator turns on semantic matching, below). Agents get ids, tags and counts, never another person's words or name.
  4. People decide. If the person who solved it left their note open to the circle, you read it at once, with their name. Otherwise they read what you are stuck on and accept or decline your intro; names appear only when both accept. Either way, another person's text reaches your agent only when you send it there yourself.

Want one person's help? Tell your agent to ask them directly: only they read it, and only you read their answer. An open note can also go on the Notes page, if you tick that: everyone in your private circles can read it any time, so what you learned reaches people who were not looking for it. A solved note can be a link card: when a public post, doc or issue fixed it, your agent adds its link, and Klatsch shows the title with the site's address beside it (it never opens the link). And nobody has to start alone: a commons is a circle with a public join link. Your sips reach it only when you tick it on the approval page.

More detail: how it works, and every flow as a diagram drawn from the tests: docs/flows.

Quick start

macOS or Linux, Node 24 or newer, and an MCP client such as Claude Code. Windows is not supported yet (the reminder hook and the token helper are POSIX shell commands).

From ChatGPT or Claude

Add https://klatsch.dev/mcp as a custom connector (ChatGPT: developer mode; Claude: Settings → Connectors), sign in to Klatsch in the page that opens, and approve the connection. Then ask in any chat, for example: *"Ask @sam on Klatsch how they set up their CI cache."* You approve it in a Klatsch card right in the chat, Sam reads and answers it in his, and the answer comes back to your chat. Add friends with "Add a friend" on the Circle page. Not yet run live with either app.

Try it locally
npx klatsch up --demo

This starts a relay on 127.0.0.1:7417 with two people, Alice and Bob, signs both in in your browser, and prints a connect command for each. Bob has already solved cursor paging in a Node.js API on Postgres, open to the circle. Run Alice's connect line in a fresh terminal, then tell her Claude Code session:

I'm stuck on pagination in my Node.js API: OFFSET paging on Postgres gets slow and skips rows. Share it on Klatsch and look for help.

Approve the share in Alice's browser, and Bob's note is on her page. Something off? See troubleshooting.

Use the hosted relay

The reference instance runs at klatsch.dev. Private circles there grow by invite: open an invite link from someone in a circle, sign in with GitHub and join. Or start in the public commons from its join link, and invite your own people later. Then, in your project directory:

npx klatsch connect --url https://klatsch.dev

It shows a code and opens the relay in your browser; sign in, type the code, read what it means and click Connect. Without a browser on this machine, open the page on another device, or make a token on the Tokens page and use --token -. The token is stored in a 0600 file and handed to Claude Code through a helper command, never written into its configuration. npx klatsch disconnect undoes it.

Using Claude Code plugins? The Klatsch plugin adds the hosted server and a /klatsch command.

Works with

klatsch connect sets up Claude Code by default; --client codex, --client copilot-vscode or --client copilot-cli sets up another agent in the same directory, with the same token file (0600, under ~/.klatsch/agents/) and the same flags (--user [--demo], or --url https:// --token - for a hosted relay). No client config holds the token: each one runs a Klatsch command that reads the file. klatsch disconnect --client removes what connect added for that client; the token is revoked (or, hosted, you are told to revoke it) once no client in the directory uses it. klatsch disconnect without --client undoes every client.

Claude CodeCodexGitHub Copilot in VS CodeGitHub Copilot CLI
What connect writeslocal-scope MCP server (claude mcp add-json), .claude/settings.local.json.codex/config.toml, .codex/hooks.json in the directory.vscode/mcp.json.mcp.json in the directory, saved tool approvals in ~/.copilot/permissions-config.json ($COPILOT_HOME)
How it gets the tokenheadersHelperhttp_headers_helperklatsch mcp-proxy, a local stdio server (VS Code has no header helper)klatsch mcp-proxy
Approving a share or introthe approval page opens from a dialoga code and a link the agent shows you (Codex speaks MCP 2025-06-18)a code and a link; the page from a dialog only if the client speaks 2026-07-28 with URL dialogs (not verified)the same as VS Code (not verified)
Wakes an idle session (watch)yes, in the terminal CLInononot verified
Reminder when you typeyes (prompt hook)yes, once you trust the hook in /hooksno (Copilot does not pass a prompt hook's output to the model)no
Klatsch tools run without a promptallow rulesapproval_mode = "approve" per toolno setting for it: choose "Always allow" at the first callsaved approvals, which Copilot keeps per repository: they cover every folder in it

Only Claude Code has been run end to end. The Codex setup was checked against the openai/codex source (main at 3026a8e, 2026-11-02, after rust-v0.166.0) and its docs; the Copilot setup against the VS Code docs (microsoft/vscode-docs 84925c3) and source (microsoft/vscode 37eba09), the GitHub Copilot CLI docs (github/docs b8fe410) and the Copilot CLI changelog up to 1.0.105. None of them has been run live with Klatsch yet; klatsch mcp-proxy is tested with the official MCP client over stdio.

Per client:

  • Codex: klatsch connect --user --client codex, then start codex in that directory, trust the project when asked (Codex reads .codex/ only in trusted projects) and run /hooks to trust the Klatsch hook (again after a reconnect changes its command). The server entry is per project, not in ~/.codex/config.toml, so every connected directory keeps its own token. Connect writes one marked block at the end of .codex/config.toml and stops if the file already defines a klatsch server some other way.
  • GitHub Copilot in VS Code: klatsch connect --user --client copilot-vscode, open the folder in VS Code, start the klatsch server when asked, and pick "Always allow" for the Klatsch tools. Connect stops, without touching it, if .vscode/mcp.json has comments or trailing commas; remove them, or add the server by hand: "servers": {"klatsch": {"type": "stdio", "command": "npx", "args": ["-y", "klatsch@ ", "mcp-proxy", "--url", " ", "--dir", " "]}} (add "--data", " " if you use one).
  • ChatGPT, claude.ai and other apps that connect by OAuth: add https:// /mcp as a custom connector (in ChatGPT, developer mode). The app opens a Klatsch page where you approve the connection; it then appears on your Tokens page, where you revoke it. Approvals of what it shares still happen on Klatsch's own pages. Not yet run live against these apps.
  • GitHub Copilot CLI: klatsch connect --user --client copilot-cli, then start copilot in that directory and trust the folder (it loads .mcp.json only in trusted folders). Claude Code also reads a project .mcp.json and asks once whether to use its servers; the klatsch server there works for it too.

The files in the directory hold paths on this machine, not the token: keep .codex/, .vscode/mcp.json and .mcp.json out of git (connect warns when git would pick one up). For the Copilot CLI, disconnecting a folder below the repository root keeps the repository's approvals, since other connected folders there may use them, and says where to remove them.

Privacy and security

  • An agent can ask, never approve. Every share and every intro is decided in the human's own signed-in web session; an approval works once, for ten minutes, only for its owner.
  • Agents never get another person's text or name. You can hand one note you read to your own agent, or choose to always get one person's notes; every "always" is listed in Settings and revoked with one click.
  • Matching is deterministic by default. A model only ever reads its own human's data. An operator can turn on semantic matching: a model inside the relay compares approved summaries in private circles and can only make a match; the approval page says so. It is off by default.
  • Public circles are opt-in per sip. A sip reaches a public circle only when you tick it on its approval page; strangers there see no member list. Klatsch never fetches a link card's link.
  • Tokens are scoped per tool, short-lived, revocable and stored as keyed hashes. The web UI runs no JavaScript and has a strict Content-Security-Policy.
  • Sealed at rest. What people wrote is encrypted in the database with a key from the server secret, so a backup or a copied database file does not show it. This is not end-to-end encryption.
  • Limits, stated plainly: whoever runs a relay can read everything on it; on your own machine, an agent with shell access runs as you. Run your own relay for a circle you do not want to trust to someone else.

The whole model, with what it does not protect against: docs/security-model.md. Found a hole? Please report it privately: SECURITY.md.

How it compares

Klatsch sits next to tools you may already use. The table describes each kind of tool as it usually works; a particular product may differ.

Who reads what you wroteWho decides it is sharedFinds the people you know
KlatschPeople in your circle, after you approve; other agents only what a person hands overYou, per sip, in your browser; the other person decides on introsYes, by invite-only circles

| Shared-m

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