Skip to main content
mcpSource-backed

Context+ MCP Server

MCP server for semantic codebase intelligence, combining AST structure, embeddings, clustering, feature hubs, restore points, and memory graph tools.

by forloopcodes · submitted by oktofeesh1·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/forloopcodes/contextplus/blob/main/README.md, https://github.com/forloopcodes/contextplus
Brand
Context+
Brand domain
github.com
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.
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.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

15 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials2Install & runtime2Review & approval115 minutes

Safety & privacy surface

Safety & privacy surface

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.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "contextplus": {
      "command": "npx",
      "args": ["-y", "contextplus"],
      "env": {
        "CONTEXTPLUS_EMBED_PROVIDER": "ollama",
        "OLLAMA_EMBED_MODEL": "nomic-embed-text"
      }
    }
  }
}

About this resource

Content

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.

Source Review

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.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "contextplus": {
      "command": "npx",
      "args": ["-y", "contextplus"],
      "env": {
        "CONTEXTPLUS_EMBED_PROVIDER": "ollama",
        "OLLAMA_EMBED_MODEL": "nomic-embed-text"
      }
    }
  }
}

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.

Source citations

Add this badge to your README

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.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/contextplus-mcp-server.svg)](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.

Field

MCP server for semantic codebase intelligence, combining AST structure, embeddings, clustering, feature hubs, restore points, and memory graph tools.

Open dossier

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.

Open dossier

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.

Open dossier

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.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandGemini MCP Tool logoGemini MCP ToolLeanCTX logoLeanCTX
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorforloopcodesDeusDatajamubcYves Gude
Added2026-06-052026-06-052026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesContext+ 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 notesSource 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.
Install
npx -y contextplus
npm install -g codebase-memory-mcp
npx -y gemini-mcp-tool
npm install -g lean-ctx-bin
Config
{
  "mcpServers": {
    "contextplus": {
      "command": "npx",
      "args": ["-y", "contextplus"],
      "env": {
        "CONTEXTPLUS_EMBED_PROVIDER": "ollama",
        "OLLAMA_EMBED_MODEL": "nomic-embed-text",
        "OLLAMA_CHAT_MODEL": "llama3.2"
      }
    }
  }
}
{
  "mcpServers": {
    "codebase-memory": {
      "command": "npx",
      "args": ["-y", "codebase-memory-mcp"]
    }
  }
}
{
  "mcpServers": {
    "gemini-cli": {
      "command": "npx",
      "args": ["-y", "gemini-mcp-tool"]
    }
  }
}
{
  "mcpServers": {
    "lean-ctx": {
      "command": "lean-ctx",
      "env": {
        "LEAN_CTX_IO_BOUNDARY_MODE": "enforce",
        "LEAN_CTX_NO_UPDATE_CHECK": "1"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.