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.
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 20/100 | Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-11-16 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 5/5 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Context Nest. Follow https://mcp.popnx.com/i/promptowl-contextnest.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (nest.promptowl.ai) · ✓ Commands checked Nov 16, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Context Nesthttps://nest.promptowl.ai/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsContext Nest
Use Context Nest and tell me what you can do for me, then show me one thing✓ If Claude says it is using Context Nest or shows a Context Nest tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Context Nesthttps://nest.promptowl.ai/mcpStart a new chat and pick Context Nest from your plugins before typing
Use Context Nest and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Context Nest or shows a Context Nest tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user contextnest https://nest.promptowl.ai/mcpYou should see Context Nest listed as connected
Use Context Nest and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Context Nest or shows a Context Nest tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Context Nest and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Context Nest or shows a Context Nest tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Context Nest and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Context Nest or shows a Context Nest tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://nest.promptowl.ai/mcpJSON settings are under “For developers” below
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 envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @promptowl/contextnest-mcp-serverBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account PromptOwl, which owns the repo
Code last changed 2 days ago
Uses AGPL-3.0
Responded in 160 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
The cloud address answered 5 of the last 5 checks · latest 160 ms · checked Nov 19, 2026
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/promptowl-contextnest)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 2 days ago, and the latest version (2.16.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
| This one Context Nest | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | AGPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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