MCP.so
Sign In
C

ContextBridge

@tijuthomas5

Repository

About ContextBridge

Local-first code retrieval for AI agents — cuts codebase context from tens of thousands of tokens to a few hundred, with zero hallucinated file paths.

#code-search#retrieval#context-management#token-optimization#codebase-indexing#local-first#rag

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "context_bridge": {
      "url": "http://127.0.0.1:8755/sse"
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is ContextBridge?

ContextBridge is a local-first code retrieval layer for AI coding agents. It indexes codebase structure via Graphify output, then exposes MCP tools that any AI client (Claude Code, Codex, Cursor, etc.) can call to get ranked files, symbols, and dependency chains — optionally validated and re-ranked by a local LLM before reaching the cloud AI.

How to use ContextBridge?

Setup runs via platform-specific batch scripts (setup_context_bridge.bat on Windows, equivalents in setup/mac/ or setup/linux/). Edit the generated config.hybrid.json to point settings.discovery.* at your source folders, re-run setup, then start the server. By default ContextBridge runs SSE at http://127.0.0.1:8755/sse; set CONTEXT_BRIDGE_TRANSPORT=stdio for stdio transport. A dashboard is available at http://127.0.0.1:8795.

Key features of ContextBridge

  • Keyword-first hybrid retrieval with guarded vector assist
  • Optional local AI analysis that validates and re-ranks results
  • Swappable profile plugins for project-specific ranking
  • MCP tools: search_context_hybrid, find_code_locations, get_module_summary, record_outcome, and more
  • Rerunnable safe setup that never overwrites existing configs

Use cases of ContextBridge

  • Replace pasting 10–50 raw source files with a few hundred tokens of ranked context
  • Ground AI agent decisions in exact file paths, symbols, and line hints
  • Reduce token costs and noise by focusing on the 3–5 files that matter
  • Decompose multi-topic prompts into compact, grounded search results

FAQ from ContextBridge

What does ContextBridge do compared to a reasoning engine?

ContextBridge is a codebase routing and retrieval tool, not a reasoning engine — it finds the right files, symbols, and connections but does not prove causality or choose the fix.

What dependencies are required?

ContextBridge indexes Graphify output (graph.json, GRAPH_REPORT.md, source-files.txt, scope-summary.md, manifest.json) plus /behavior/ docs. The optional local AI stage uses Ollama by default but also supports Anthropic, OpenAI, or OpenRouter.

What transport does ContextBridge use?

SSE transport on http://127.0.0.1:8755/sse is recommended for multiple clients to share one server. Stdio transport is supported by setting CONTEXT_BRIDGE_TRANSPORT=stdio before starting.

Where does my codebase data live?

All indexing is local — ContextBridge builds its index from local Graphify output and docs; raw source files are never indexed. The index is refreshed by re-running setup after each Graphify update.

Are there any limitations I should know?

Dashboard live stats can lag up to ~15 seconds, and history lists (recent events, missed files, failed queries) show only the most recent 1000 entries — both are intentional performance tradeoffs, not data loss.

Frequently asked questions

What does ContextBridge do compared to a reasoning engine?

ContextBridge is a codebase routing and retrieval tool, not a reasoning engine — it finds the right files, symbols, and connections but does not prove causality or choose the fix.

What dependencies are required?

ContextBridge indexes Graphify output (graph.json, GRAPH_REPORT.md, source-files.txt, scope-summary.md, manifest.json) plus /behavior/ docs. The optional local AI stage uses Ollama by default but also supports Anthropic, OpenAI, or OpenRouter.

What transport does ContextBridge use?

SSE transport on `http://127.0.0.1:8755/sse` is recommended for multiple clients to share one server. Stdio transport is supported by setting `CONTEXT_BRIDGE_TRANSPORT=stdio` before starting.

Where does my codebase data live?

All indexing is local — ContextBridge builds its index from local Graphify output and docs; raw source files are never indexed. The index is refreshed by re-running setup after each Graphify update.

Are there any limitations I should know?

Dashboard live stats can lag up to ~15 seconds, and history lists (recent events, missed files, failed queries) show only the most recent 1000 entries — both are intentional performance tradeoffs, not data loss.

Comments

Basic information

License

NOASSERTION

Transports

stdio

Author

tijuthomas5

Submitted by

Tiju Thomas

More MCP servers

Clipkit

clipkit-video

The video infra for AI agents: compose motion-graphics video from one JSON document (open Clipkit Protocol), validate before it costs anything, preview stills in-chat, and render deterministic MP4s on a GPU runtime.

11

Subtext

Subtext by Fullstory

Session replay, built for agents. Subtext is agentic session review: it captures production sessions of your app and connects them to your coding agent — Claude Code, Cursor, Codex, Devin, your own harness — so it can

9

Perfex CRM

themesic

Turn Perfex CRM into an AI-ready workspace. This MCP server exposes your full REST API to Claude, ChatGPT and any AI agent, so leads, invoices and tasks are one prompt away.

1

Medplum

medplum

Medplum is a healthcare platform that helps you quickly develop high-quality compliant applications.

2.5K
F

fhirHydrant

faulkj

Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.

14