Which integrations are available for this server?

Enables high-performance execution of JavaScript and TypeScript in a sandboxed environment to process and summarize large outputs. Allows listing containers and monitoring resource usage through sandboxed command execution with credential passthrough. Analyzes repository history and logs to provide summaries of commits and file changes without loading the entire log into context. Interfaces with the GitHub CLI to fetch and summarize issues, pull requests, and repository metadata. Interacts with Kubernetes clusters to show running pods and resource metrics via sandboxed kubectl commands. Executes JavaScript code in a sandboxed environment to summarize files and raw data inputs. Analyzes project dependencies and package files to identify large modules and project configuration. Runs Perl scripts in an isolated sandbox to filter and summarize large text outputs. Executes PHP code in a sandboxed environment to process data and return concise summaries. Performs data analysis and file processing using sandboxed Python scripts to generate summaries of large datasets. Fetches, indexes, and searches React documentation to provide specific code examples and technical patterns. Runs Ruby code in a sandbox to process complex data and generate summarized results. Provides sandboxed Rust execution for high-performance processing and summarization of large data sources.

How do I use Context Mode?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Context Mode Analyze the last 500 lines of app.log for any database errors" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Context Mode

Stop losing context to large outputs.

npm License: MIT

Run tests without burning 5K tokens. Query docs without loading raw HTML. Debug logs without reading 45KB of noise. Only summaries reach Claude — everything else stays in the sandbox.

Without Context Mode With Context Mode ───────────────────── ──────────────────── Playwright snapshot → 56 KB into context → 299 B summary GitHub issues (20) → 59 KB into context → 1.1 KB summary Access log (500) → 45 KB into context → 155 B summary Context7 docs → 6 KB into context → 261 B summary Total: 166 KB = 42K tokens gone Total: 1.8 KB = ~450 tokens

Install

claude mcp add context-mode -- npx -y context-mode

Restart Claude Code. Done. You now have 5 tools that intercept large outputs and return only what matters.

/plugin marketplace add mksglu/claude-context-mode /plugin install context-mode@claude-context-mode

Installs the MCP server + a skill that automatically guides Claude to route large outputs through Context Mode. No prompting needed.

claude --plugin-dir ./path/to/context-mode

What It Does

Every MCP tool call dumps raw data into your 200K context window. With 81+ tools active, 143K tokens (72%) get consumed before your first message. Context Mode intercepts these operations, processes data in isolated subprocesses, and returns only what you need.

Result: 315 KB raw data becomes 5.4 KB of context across 14 real scenarios — 98% savings.

Metric	Without	With
Context consumed per session	315 KB	5.4 KB
Time before slowdown	~30 min	~3 hours
Context remaining after 45 min	60%	99%

Tools

`execute` — Run code in sandbox

Execute code in 10 languages (JS, TS, Python, Shell, Ruby, Go, Rust, PHP, Perl, R). Only stdout enters context.

execute({ language: "shell", code: "gh pr list --json title,state | jq length" }) → "3" ← 2 bytes instead of 8KB

Add intent for large outputs — Context Mode filters to relevant sections automatically:

execute({ language: "shell", code: "cat app.log", intent: "database connection error" }) → matching sections + searchable terms ← 500B instead of 100KB

Authenticated CLIs work out of the box — gh, aws, gcloud, kubectl, docker credentials pass through. Bun auto-detected for 3-5x faster JS/TS.

`execute_file` — Process files without loading

File contents stay in the sandbox as FILE_CONTENT. Your code summarizes. Only the summary enters context.

execute_file({ path: "access.log", language: "python", code: "..." }) → "200: 312 | 404: 89 | 500: 14" ← 30 bytes instead of 45KB

`index` + `search` — Searchable knowledge base

Index documentation into FTS5 with BM25 ranking. Search returns exact code blocks — not summaries.

index({ content: <60KB React docs>, source: "React useEffect" }) → "Indexed 33 sections (15 with code)" ← 40 bytes search({ query: "useEffect cleanup function" }) → exact code example with heading context ← 500 bytes instead of 60KB

`fetch_and_index` — Fetch URLs into knowledge base

Fetches, converts HTML to markdown, indexes. Raw content never enters context. Use instead of WebFetch or Context7 when you need to reference docs multiple times.

fetch_and_index({ url: "https://react.dev/reference/react/useEffect" }) → "Indexed 33 sections (15 with code)" ← 40 bytes instead of 60KB

Example Prompts

Just ask naturally — Claude routes through Context Mode automatically when it saves tokens.

"Analyze the last 50 commits and find the most frequently changed files" "Read the access log and break down requests by HTTP status code" "Run the test suite and give me a pass/fail summary" "Fetch the React useEffect docs and find the cleanup pattern" "List all Docker containers with their memory usage" "Find all TODO comments across the codebase" "Analyze package-lock.json and find the 10 largest dependencies" "Show running Kubernetes pods and their restart counts"

Real-World Benchmarks

Operation	Raw	Context	Savings
Playwright `browser_snapshot`	56.2 KB	299 B	99%
GitHub Issues (20)	58.9 KB	1.1 KB	98%
Access log (500 requests)	45.1 KB	155 B	100%
Context7 React docs	5.9 KB	261 B	96%
Analytics CSV (500 rows)	85.5 KB	222 B	100%
Git log (153 commits)	11.6 KB	107 B	99%
Test output (30 suites)	6.0 KB	337 B	95%

Full benchmark data with 21 scenarios →

How It Works

┌─────────────┐ stdio / JSON-RPC ┌─────────────────────────────────┐ │ Claude Code │ ◄─────────────────────► │ Context Mode MCP Server │ │ │ tool calls/results │ │ └─────────────┘ │ Sandboxed subprocesses │ │ • 10 language runtimes │ │ • Auth passthrough (gh, aws…) │ │ • Intent-driven search │ │ │ │ SQLite FTS5 knowledge base │ │ • BM25 ranking │ │ • Porter stemming │ │ • Heading-aware chunking │ └─────────────────────────────────┘

Each execute call spawns an isolated subprocess — scripts can't access each other, but authenticated CLIs (gh, aws, gcloud) find their configs through secure credential passthrough.

Requirements

Node.js 18+
Claude Code with MCP support
Optional: Bun (auto-detected, 3-5x faster JS/TS)

Development

git clone https://github.com/mksglu/claude-context-mode.git cd claude-context-mode && npm install npm test # 100+ tests across 4 suites npm run test:all # full suite

License

MIT

Context Mode

Context Mode

Install

What It Does

Tools

`execute` — Run code in sandbox

`execute_file` — Process files without loading

`index` + `search` — Searchable knowledge base

`fetch_and_index` — Fetch URLs into knowledge base

Example Prompts

Real-World Benchmarks

How It Works

Requirements

Development

License

Resources

Latest Blog Posts

MCP directory API

Context Mode

Install

What It Does

Tools

execute — Run code in sandbox

execute_file — Process files without loading

index + search — Searchable knowledge base

fetch_and_index — Fetch URLs into knowledge base

Example Prompts

Real-World Benchmarks

How It Works

Requirements

Development

License

Resources

Latest Blog Posts

MCP directory API

`execute` — Run code in sandbox

`execute_file` — Process files without loading

`index` + `search` — Searchable knowledge base

`fetch_and_index` — Fetch URLs into knowledge base