
Context Mode Marketplace
- Updated August 10, 2026
- zhangyejian/ContextModeWithProxy
ContextModeWithProxy is a Claude Code and Codex plugin fork of context-mode v1.0.151 that adds default Clash/mihomo proxy environment variables for containerized MCP fetch and execute workflows.
About
context-mode is a modified distribution of mksglu/context-mode packaged as a Claude Code marketplace plugin for developers who run agents inside containers behind a local Clash or mihomo proxy. The marketplace manifest describes sandboxed code execution in eleven languages, an FTS5 knowledge base with BM25 ranking, and intent-driven search tools such as ctx_execute and ctx_fetch_and_index. This fork adds default HTTP_PROXY, HTTPS_PROXY, and ALL_PROXY values in start.mjs, Codex MCP manifests, and sandbox subprocesses, plus a curl-based fetch path when proxies are set because Node 22 fetch ignores proxy variables. Install via marketplace zhangyejian/ContextModeWithProxy when direct outbound fetches fail but proxied access works. Avoid it for untrusted URL ingestion unless you accept relaxed SSRF protections documented in MODIFICATIONS.md compared to upstream.
- Fork of mksglu/context-mode v1.0.151 with proxy defaults for Clash/mihomo
- Marketplace cites 11-language sandbox execution and FTS5 BM25 knowledge base
- Injects HTTP_PROXY, HTTPS_PROXY, ALL_PROXY into start.mjs and Codex mcp.json
- Proxy-aware ctx_fetch_and_index uses curl when proxy env vars are present
- ctx_execute, ctx_execute_file, ctx_batch_execute inherit proxy in sandbox subprocesses
Context Mode by the numbers
- Data as of Aug 11, 2026 (Skillselion catalog sync)
/plugin marketplace add zhangyejian/ContextModeWithProxyAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | August 10, 2026 |
|---|---|
| Repository | zhangyejian/ContextModeWithProxy ↗ |
How do you run context-mode MCP behind a Clash proxy?
Run context-mode MCP with Clash/mihomo proxy defaults for sandboxed execution, FTS5 search, and proxied ctx_fetch_and_index in containerized Codex or Claude Code.
Who is it for?
Developers running context-mode or Codex MCP inside containers where child processes miss shell proxy variables and outbound fetch fails without Clash defaults.
Skip if: Direct-network environments that already inherit proxy settings correctly, or untrusted URL ingestion where upstream SSRF stripping should remain enabled.
What you get
Proxy-aware context-mode MCP sessions with successful ctx_fetch_and_index indexing and ctx_execute fetches through HTTP_PROXY and ALL_PROXY defaults.
- indexed fetch sources
- proxy-aware sandbox execution logs
By the numbers
- Based on upstream context-mode v1.0.151
- Default proxy ports 7890 for HTTP/HTTPS and 7891 for ALL_PROXY socks5h
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Pick ContextModeWithProxy for proxied container MCP sessions; use upstream context-mode when direct-network SSRF protections should stay strict.
FAQ
Which upstream version is ContextModeWithProxy based on?
ContextModeWithProxy README states it modifies mksglu/Context Mode v1.0.151 and remains under the Elastic License 2.0 with upstream copyright preserved.
What default proxy ports does ContextModeWithProxy assume?
ContextModeWithProxy defaults to HTTP_PROXY and HTTPS_PROXY on http://127.0.0.1:7890 and ALL_PROXY socks5h://127.0.0.1:7891 when variables are unset.
Why does ctx_fetch_and_index use curl in this fork?
ContextModeWithProxy routes ctx_fetch_and_index through curl when proxy variables exist because Node 22 fetch does not honor HTTP_PROXY, while curl does in proxied containers.