Ocular vs Context Mode
A side-by-side look at the Ocular and Context Mode MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ocular for coding agents work as a local process; choose Context Mode for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ocular when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OCULAR_BASE_URL, OCULAR_API_KEY, OCULAR_MODEL. - You want tools like
analyze_image, extract_text_from_image, analyze_ui_screenshot.
Choose Context Mode when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ctx_batch_execute, ctx_execute, ctx_execute_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 60/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OCULAR_BASE_URLOCULAR_API_KEYOCULAR_MODEL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 32,137 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | 10 |
| Full listing | View Ocular | View Context Mode |
Tools & capabilities
Ocular tools 8
analyze_imageAnalyze a general image and return structured JSON for a coding agent.extract_text_from_imageExtract OCR text from screenshots, documents, tables, terminal output, or code images.analyze_ui_screenshotAnalyze a webpage, app, UI, or design mockup screenshot for frontend implementation work.diagnose_error_screenshotAnalyze error, terminal, console, browser, or build failure screenshots.compare_ui_screenshotsCompare two UI screenshots and return implementation-useful visual differences.extract_table_from_imageExtract visible table data from an image as structured JSON, Markdown, or CSV-oriented output.analyze_chart_imageAnalyze a chart image and return labels, trends, approximate values, and limitations.create_upload_sessionReturns upload instructions for the binary side channel (use this to analyze LOCAL image files without base64 corruption). Before uploading, verify the local file exists and is non-empty with Bash (e.g. `ls -la <path>` or `test -f <path> && stat -c %s <path>`). Then PUT the raw bytes to the returned upload_url with curl --data-binary (NOT base64); the response gives a file_id to pass to any vision tool. Stateless -- call once to learn the endpoint.
Context Mode tools 10
ctx_batch_executeRun multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches.ctx_executeRun code in 12 languages. Only stdout enters context.ctx_execute_fileProcess files in sandbox. Raw content never leaves.ctx_indexChunk markdown into FTS5 with BM25 ranking.ctx_searchQuery indexed content with multiple queries in one call.ctx_fetch_and_indexFetch URL, chunk and index. Cache reuses content within TTL (default 24h, override per-call with `ttl: <ms>`). `ttl: 0` or `force: true` to bypass. Pass `requests: [{url, source}, ...]` + `concurrency: 1-8` for parallel multi-URL.ctx_statsShow context savings, call counts, and session statistics.ctx_doctorDiagnose installation: runtimes, hooks, FTS5, versions.ctx_upgradeUpgrade to latest version from GitHub, rebuild, reconfigure hooks.ctx_purgePermanently deletes all indexed content from the knowledge base.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ocular
{
"mcpServers": {
"ocular": {
"command": "npx",
"args": [
"-y",
"ocular-mcp"
],
"env": {
"OCULAR_BASE_URL": "YOUR_OCULAR_BASE_URL_HERE",
"OCULAR_API_KEY": "YOUR_OCULAR_API_KEY_HERE",
"OCULAR_MODEL": "YOUR_OCULAR_MODEL_HERE"
}
}
}
}
Context Mode
{
"mcpServers": {
"context-mode": {
"command": "npx",
"args": [
"-y",
"context-mode"
]
}
}
}
Frequently asked questions
Ocular is categorized under Coding Agents and uses a local stdio subprocess. Context Mode belongs to Coding Agents and uses a local stdio subprocess. Pick Ocular for coding agents work and Context Mode for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ocular has no declared pricing — check the project's own site. Context Mode is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ocular and context-mode as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ocular has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Context Mode has 69/100 (Great) with 2 views, 0 installs and 32,137 GitHub stars.