Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes., The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving., Static analysis tools may invoke local compilers, linters, or language tools depending on the repository., Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends., External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.
Privacy notes
Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider., Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans., Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts., Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.
Author
forloopcodes
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, third-party handling.
5 areas
SafetyLocal filesContext+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes.
SafetyData retentionThe `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving.
SafetyGeneralStatic analysis tools may invoke local compilers, linters, or language tools depending on the repository.
SafetyCredentials & tokensRuntime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends.
SafetyThird-party handlingExternal embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.
PrivacyCredentials & tokensSource code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider.
PrivacyCredentials & tokensProprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans.
PrivacyCredentials & tokensKeep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts.
PrivacyData retentionReview `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.
Safety notes
Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes.
The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving.
Static analysis tools may invoke local compilers, linters, or language tools depending on the repository.
Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends.
External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.
Privacy notes
Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider.
Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans.
Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts.
Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.
Prerequisites
Node.js and npx available to the MCP client runtime.
A repository or workspace you are authorized to index and expose to an MCP client.
Ollama embedding model available, or an approved OpenAI-compatible embedding provider and API key.
Static analysis tools installed if you want Context+ to run native linters or compilers.
Code-write, restore-point, and memory-graph behavior reviewed before enabling in sensitive repositories.
Context+ is an MCP server for semantic and structural codebase intelligence. It
combines AST parsing, semantic embeddings, spectral clustering, Obsidian-style
feature hubs, static analysis, restore points, and memory graph tools so Claude
can navigate large repositories with less file-by-file context loading.
The upstream README documents npx -y contextplus, bunx contextplus, IDE MCP
config generation, Ollama and OpenAI-compatible embedding providers, runtime
caches, memory graph tools, and the propose_commit write path with shadow
restore points.
These sources were reviewed on 2026-06-05. Prefer the live repository,
README, package metadata, and NPM registry metadata for current package version,
command names, tools, embedding provider settings, cache behavior, and supported
agent config targets.
Features
Return structural AST trees and file skeletons.
Search code semantically by meaning or identifier.
Navigate clustered code areas with semantic labels.
Trace symbol blast radius across files and line ranges.
Run static analysis for supported language ecosystems.
Propose code changes with validation and shadow restore points.
Search and traverse a memory graph with typed relations.
Generate MCP config files for supported coding agents.
Cache file, identifier, and call-site embeddings for reuse.
If using an OpenAI-compatible embedding provider, configure the provider, API
key, base URL, embedding model, and optional chat model according to the upstream
README. Restart the MCP client after adding the server.
Use Cases
Ask Claude to find code by concept rather than exact text.
Inspect API surfaces through file skeletons without reading full bodies.
Trace every place a symbol is imported or used before refactoring.
Group a large repository into semantic feature areas.
Run static analysis before accepting a proposed change.
Store and retrieve feature notes through memory graph traversal.
Use shadow restore points to undo a Context+ proposed change.
Safety and Privacy
Context+ can read source files, create persistent caches, invoke static-analysis
tools, and write code through propose_commit. Review tool calls carefully in
repositories containing proprietary code, customer data, secrets, or production
configuration.
Local embedding with Ollama can keep source-derived text on the machine, while
OpenAI-compatible providers may receive snippets, identifiers, prompts, and
cluster-labeling context. Make the provider choice deliberately, and keep API
keys out of committed config files.
Duplicate Check
No forloopcodes/contextplus entry, contextplus package entry, or matching
source URL was found in content/mcp.
Show that Context+ MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/contextplus-mcp-server)
How it compares
Context+ MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
High-performance MCP server that indexes codebases into a persistent knowledge graph for structural search, call tracing, architecture summaries, dead-code detection, and cross-repo analysis.
Stdio MCP server that lets Claude ask the Google Gemini CLI for large-file, codebase, brainstorming, and sandboxed analysis while preserving MCP tool and prompt workflows inside Claude Code or compatible MCP clients.
Local-first context-engineering MCP server and CLI that gives Claude token-efficient file reads, shell-output compression, code search, graph queries, persistent session memory, context packaging, verification tools, and dashboard-style token accounting through a single Rust binary.
✓Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes.
The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving.
Static analysis tools may invoke local compilers, linters, or language tools depending on the repository.
Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends.
External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.
✓Codebase Memory MCP reads source files across indexed repositories and writes MCP entries, instruction files, skills, hooks, and agent configuration files during install.
The background watcher and auto-index features can keep graph data updated as source files change.
The optional graph UI exposes a local visualization server on a localhost port.
Shared graph artifacts and SQLite databases can persist source metadata after an MCP session ends.
Verify downloaded release binaries, checksums, signatures, and provenance before running them in sensitive environments.
✓Gemini MCP Tool runs locally but invokes the Gemini CLI, so prompts, file references, and command output can leave the local machine through the configured Google Gemini account or API path.
The `ask-gemini` tool can pass `@` file or directory references to Gemini CLI; current source checks that references stay under the working directory, but users should still scope prompts carefully.
Sandbox mode is exposed as an option on `ask-gemini` and forwards the Gemini CLI sandbox flag; review generated scripts, network calls, package installs, and filesystem changes before relying on sandboxed output.
Change mode can generate structured edit suggestions for Claude to apply; inspect proposed OLD/NEW replacements before applying them to source files.
Treat the project as an unofficial third-party bridge, not an official Google MCP server.
✓LeanCTX can read local files, run shell commands invoked through its tools, cache outputs, install shell/editor hooks, and persist session state.
Review generated MCP and shell-hook changes before enabling them across all agents or shells.
Keep path jail enforcement enabled for normal use, and allow extra roots only when a project genuinely needs them.
Disable or restrict command-execution and unsafe I/O tools for regulated repositories, untrusted workspaces, or shared team environments.
Treat compressed shell output and cached reads as summaries; switch to full reads or raw command output when exact source text matters.
Privacy notes
✓Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider.
Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans.
Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts.
Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.
✓Source code, filenames, paths, symbols, comments, imports, routes, call graphs, architecture summaries, ADRs, graph queries, prompts, and tool outputs may be visible to the MCP client and model provider.
Persistent graph databases and shared artifacts can retain proprietary architecture, internal package names, route names, service boundaries, and accidentally committed secrets.
Auto-indexing broad workspace roots can include unrelated private repositories or generated files.
Avoid committing shared graph artifacts unless the repository owners explicitly approve storing derived code intelligence in version control.
✓Prompts, selected source files, directory context, code snippets, local paths, command output, change-mode chunks, and brainstorming context may be sent to Gemini CLI and the configured Gemini service.
Avoid referencing `.env` files, credentials, private keys, customer data, unreleased product plans, or regulated datasets in `@` references.
The MCP server and Gemini CLI may log execution details locally; protect terminal history, MCP client logs, and Gemini CLI configuration files.
Google account, project, retention, and telemetry behavior depends on the user's Gemini CLI configuration and Google service terms.
✓Local code, file paths, command output, search terms, session notes, context packages, knowledge graph data, token metrics, and dashboard statistics can be sent to the MCP client and model.
LeanCTX stores local stats and session state under its own configuration/data directories; protect these files if they contain project decisions, findings, or sensitive paths.
Secret-like paths are blocked or role-gated by default according to upstream security docs, but users should still avoid prompting agents to read credentials, private keys, tokens, or ignored files.
The upstream security policy describes optional update checks and opt-in anonymous stats sharing; disable network checks when working in confidential or offline environments.
Prerequisites
Node.js and npx available to the MCP client runtime.
A repository or workspace you are authorized to index and expose to an MCP client.
Ollama embedding model available, or an approved OpenAI-compatible embedding provider and API key.
Static analysis tools installed if you want Context+ to run native linters or compilers.
A local repository or workspace you are authorized to index.
Platform-compatible Codebase Memory MCP release binary verified before use.
Agent configuration write access reviewed before running the installer.
Sensitive paths, generated files, vendored code, secrets, and private repositories reviewed before indexing.
Node.js 16 or newer.
Google Gemini CLI installed, authenticated, and configured before starting the MCP server.
A Claude Code, Claude Desktop, or compatible MCP client configuration that can run stdio servers.
Review of any `@file` or `@directory` references before sending prompts through Gemini CLI.
npm for the `lean-ctx-bin` package, or another upstream-supported install path such as release binaries, Homebrew, Cargo, or AUR.
A local repository workspace where LeanCTX is allowed to read files, run configured shell commands, and store session metadata.
Review of generated MCP client config, shell hooks, per-project `.lean-ctx.toml`, and global `~/.config/lean-ctx/config.toml`.
Explicit allow-listing for any paths outside the current project root that LeanCTX should be permitted to access.