World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Ask the people you know through your AI, and find who already solved it. People approve every share.
作者提供的原文
此项在“连接 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)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Klatschhttps://klatsch.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsKlatsch
用 Klatsch 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Klatschhttps://klatsch.dev/mcp开启新聊天,输入前先从插件列表中选择 Klatsch
用 Klatsch 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user klatsch https://klatsch.dev/mcp应能看到 Klatsch 在列表中并显示已连接
用 Klatsch 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Klatsch 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Klatsch 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Klatsch,或回答中出现 Klatsch 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://klatsch.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user klatsch https://klatsch.dev/mcpCursor (~/.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 upClaude 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 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 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
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月21日
注册名称已通过域名 klatsch.dev 验证(注册中心会核实域名所有权)
代码最后更新于昨天
使用 Apache-2.0
在 577 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
OSV.dev 中没有 klatsch@0.1.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/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
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Klatsch | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
looking, solved), a few tags from a fixed vocabulary, at most 200 characters.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.
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).
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.
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.
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.
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 Code | Codex | GitHub Copilot in VS Code | GitHub Copilot CLI | |
|---|---|---|---|---|
| What connect writes | local-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 token | headersHelper | http_headers_helper | klatsch mcp-proxy, a local stdio server (VS Code has no header helper) | klatsch mcp-proxy |
| Approving a share or intro | the approval page opens from a dialog | a 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 CLI | no | no | not verified |
| Reminder when you type | yes (prompt hook) | yes, once you trust the hook in /hooks | no (Copilot does not pass a prompt hook's output to the model) | no |
| Klatsch tools run without a prompt | allow rules | approval_mode = "approve" per tool | no setting for it: choose "Always allow" at the first call | saved 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:
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.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).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.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.
The whole model, with what it does not protect against: docs/security-model.md. Found a hole? Please report it privately: SECURITY.md.
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 wrote | Who decides it is shared | Finds the people you know | |
|---|---|---|---|
| Klatsch | People in your circle, after you approve; other agents only what a person hands over | You, per sip, in your browser; the other person decides on intros | Yes, by invite-only circles |
| Shared-m