World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
A shared, governed brain for AI agents: versioned context with approvals, local or hosted.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-16 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Context Nest。按照 https://mcp.popnx.com/i/promptowl-contextnest.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(nest.promptowl.ai) · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Context Nesthttps://nest.promptowl.ai/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsContext Nest
用 Context Nest 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Context Nest,或回答中出现 Context Nest 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Context Nesthttps://nest.promptowl.ai/mcp开启新聊天,输入前先从插件列表中选择 Context Nest
用 Context Nest 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Context Nest,或回答中出现 Context Nest 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user contextnest https://nest.promptowl.ai/mcp应能看到 Context Nest 在列表中并显示已连接
用 Context Nest 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Context Nest,或回答中出现 Context Nest 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Context Nest 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Context Nest,或回答中出现 Context Nest 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Context Nest 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Context Nest,或回答中出现 Context Nest 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://nest.promptowl.ai/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user contextnest https://nest.promptowl.ai/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"contextnest": {
"url": "https://nest.promptowl.ai/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"contextnest": {
"type": "http",
"url": "https://nest.promptowl.ai/mcp"
}
}
}Claude Code
claude mcp add --scope user contextnest -- npx -y @promptowl/contextnest-mcp-serverClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"contextnest": {
"command": "npx",
"args": [
"-y",
"@promptowl/contextnest-mcp-server"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"contextnest": {
"command": "npx",
"args": [
"-y",
"@promptowl/contextnest-mcp-server"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"contextnest": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@promptowl/contextnest-mcp-server"
]
}
}
}CONTEXTNEST_VAULT_PATH env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 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月20日
注册名称已通过 GitHub 账户 PromptOwl 验证,该账户拥有此仓库
代码最后更新于前天
使用 AGPL-3.0
在 160 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 5 次检查中有 5 次响应 · 最近一次 160 ms · 检查于 2026年11月19日
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/promptowl-contextnest)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于前天,最新版本(2.16.0)于4天前进入注册中心。
支持 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.
| 本项 Context Nest | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | AGPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Governed context for your AI agents — not memory.
by [PromptOwl](https://promptowl.ai) | Website | Whitepaper | Specification | Discord
MCP server for Context Nest — gives AI agents direct access to your context vault via the Model Context Protocol. Every node is typed, versioned, and hash-chained, so what the agent reads is governed and auditable, not a fuzzy memory blob. Supports all node types — documents, source nodes, and skill nodes. Exposes 47 tools over stdio transport: 27 canonical context_* tools, 9 vault, review and drift tools, and 11 deprecated aliases.
New in 2.2.1 —
context_folderslists the vault's folders and their
document counts without opening a document, and
context_listtakes a
folderto read one folder instead of crawling the whole vault. Writes on a
large vault no longer slow down as its checkpoint chain grows.
New in 2.1 — the server now installs zero dependencies, down from 97 packages at depth 11.
context_importalso gained the whole folder-import flow, so an existing folder of markdown can be imported in one call.
New in 2.0 — sixteen canonical
context_*tools are generated straight from the engine's operation catalog, so this server, thectxCLI and the PromptOwl cloud now advertise the same names, schemas and error codes. The older tools still work and are marked deprecated. See Upgrading to 2.0.
Run it directly, no install:
npx -y @promptowl/contextnest-mcp-server /path/to/your/vault
Or install globally:
npm install -g @promptowl/contextnest-mcp-server
Zero dependencies, no install scripts. Everything the server needs is compiled into the published bundle, so the install pulls one package and executes none of our code. A stdio server never touches the SDK's express, hono, ajv or jose transports, and they are no longer shipped. Every bundled package is listed with its version and licence in DEPENDENCIES.md.
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": { "contextnest": { "command": "contextnest-mcp", "args": ["/path/to/your/vault"] } } }
claude mcp add contextnest -- contextnest-mcp /path/to/your/vault
gemini mcp add contextnest -- contextnest-mcp /path/to/your/vault
contextnest-mcp /path/to/your/vault
The positional argument may also be a registered alias (see the CLI's ctx vault add), in which case the path is looked up in the central registry (~/.contextnest/config.yaml):
contextnest-mcp work
Or via environment variable:
# Absolute path
CONTEXTNEST_VAULT_PATH=/path/to/vault contextnest-mcp
CONTEXTNEST_VAULT=work contextnest-mcp
The vault is resolved with this precedence: CONTEXTNEST_VAULT (alias) → CONTEXTNEST_VAULT_PATH (path) → positional argument (alias or path) → a vault found above the current directory → the registry's default alias → the current directory.
context_*)Name, description and input schema for each of these come from the engine's operation catalog, so this surface cannot drift from the CLI or the cloud. Prefer them over the legacy tools below.
| Tool | Description |
|---|---|
context_init | Open a vault: its CONTEXT.md instructions, configuration, path, and what it holds (totals, counts by type and status, tag set). include_nodes to also list nodes |
context_nests | List every nest in the central registry — alias, path, description, which is default, whether it exists |
context_skill | Render a type: skill node for an agent harness (Claude Code, Cursor, Codex, raw) — trigger becomes the harness matcher |
context_skill_install | Build the file manifest that installs a vault skill. Loader mode (default) fetches at runtime and cannot drift; full embeds an offline copy that will |
context_structure | The nest's structure rules — allowed folders, node types, folder/file-name formats, templates and required sections/files. folder resolves one folder's rule with its template body; report lists existing content that breaks the rules. Writes that break an enforced rule are refused |
context_get | Read one node. include_raw for the exact stored bytes, verify_checksum to detect drift on read, allow_rejected to read a retired node. Returns last_edit: who made the version served (the human, plus the agent that made the call) |
context_list | List nodes with folder / type / status / tag filters. Takes folder (a path relative to the vault root — the id prefix) and recursive, an array of types, include_retired, full, limit, and include_last_edit (who last edited each row) |
context_folders | List the vault's folders and their document counts, read from directory entries without opening a document. folder to scope it, recursive: false for the immediate children only |
context_search | Search published nodes, best match first. mode: lexical (stemmed BM25, default), semantic (embeddings), hybrid (RRF of both, exact title/#tag matches pinned); rerank re-scores the top hits. Each hit carries score + per-signal scores |
context_embed | Build/refresh the embedding index for semantic/hybrid search — published nodes only, re-embeds only new/changed versions, prunes the rest (rebuild to start over) |
context_query | Selector query with graph traversal. include_drafts for authoring surfaces |
context_resolve | Resolve a selector to full bodies within a token budget |
context_versions | List a document's version history (new capability — nothing exposed this before) |
context_reconstruct | Reconstruct a specific version. Refuses a version the history does not contain, instead of returning a neighbour's content |
context_packs | List packs, each with its includes and excludes |
context_verify | Verify every hash chain in the vault and rebuild every recorded version (version_unreconstructable when one cannot be rebuilt). Forgotten versions verify hash-only (tombstoned) |
context_forget | Forget a node (spec §6.3): erase every version's content, keep the hashes so verify still passes, leave an empty status: forgotten stub every URI resolves to. reason_code is a closed set, never free text. Later republish/re-import of the content is refused |
context_forget_log | The forget audit trail: who, when, reason code, which versions. Never the content |
context_archive | Archive a node: out of lists and retrieval, history kept (spec §1.13) |
context_unarchive | Bring an archived node back in the status it left |
context_move | Move a node to another folder with its history and any PDF |
context_create | Create a node. Mint your own id, keep it a draft with publish: false, set an initial status, record a note, or supply a full skill block |
context_update | Update a node — rename via title, set status, stamp an explicit version, clear a metadata key by sending null. Defaults to *not* publishing when status names a non-published state |
context_publish | Publish a node (bump version, seal checkpoint); takes a note, returns the chain_hash |
context_delete | Delete a node and its version history, recorded in the forget audit log (purge: true for none); returns the deleted node's title |
context_import_pdf | Import a PDF (bytes_base64) as a type: pdf node: extracted text as the body ( markers; empty + text_layer: false for a scan), the PDF stored beside it and bound by SHA-256. Pass id of an existing pdf node for a new version — the old binary is kept in history |
context_import | Bulk create-and-publish. Takes documents (title + content) and/or ids (files already in the vault, published as-is) — a mixed batch seals one checkpoint and regenerates the index once |
client — attributing a callEvery tool above takes an optional client object naming the calling agent and its session, plus any custom scalar keys:
context_create({
title: "API Design", content: "…", client: { agent: "claude-code", session_id: "s-9f2" } })
A write that publishes records it on the version-history entry it seals, so context_versions can answer *which agent wrote v7, in which session*; a graph read stamps it on the access traces it emits.
Every field is optional — client itself, and agent/session_id within it. Send none, one, or all.
You usually do not need to send it. The server fills both fields from what the connection already tells it: agent from the clientInfo.name in your initialize handshake, and session_id from a per-process id — over stdio one server process is one client connection, so every call sharing that id really did come from one session. Anything you send wins, merged per key: supply just agent and you keep it while still getting a session id.
| Env var | Effect |
|---|---|
CONTEXTNEST_NO_ATTRIBUTION=1 | Server derives nothing; nothing is recorded unless a caller sends its own client |
CONTEXTNEST_AGENT | Overrides the agent the handshake reports |
CONTEXTNEST_SESSION_ID | Overrides the per-process session id |
Precedence per key: caller > env > connection. With attribution off and no caller value, the client key is left off the record entirely rather than written as {} — "not attributed" and "attributed to nobody" are different claims, and history should only make the first. The opt-out matters because what gets derived lands in an append-only history: an operator who does not want their client's name recorded in a vault needs to say so before the first write, not scrub it after.
It is a label, never an identity claim — clientInfo.name is your self-report, the server authenticates neither, and it never authorizes from either — and it is not an input to any hash chain. Note that client describes the CALL; metadata on context_create / context_update is frontmatter and describes the DOCUMENT. See spec §9.4.
| Tool | Description |
|---|---|
document_format | Get the document format spec (call before creating docs) |
read_index | Return the context.yaml graph index |
read_pack | Resolve and return a context pack |
list_checkpoints | List recent checkpoints |
context_review | Controls the review gate. It can list held writes, approve or reject one by id, and turn the gate off or on. |
Registered and behaving exactly as before, so existing clients keep working. They will be removed in a future major.
| Deprecated | Use instead |
|---|---|
vault_info | context_init |
read_document | context_get |
list_documents | context_list |
search | context_search |
resolve | context_resolve |
read_version | context_reconstruct |
verify_integrity | context_verify |
create_document | context_create |
| update_document | `context_up