Context Lens

Created By
cornelcroi7 months ago
Overview

What is Context Lens?

Context Lens is a tool that transforms any content into a searchable knowledge base for AI assistants, enabling them to understand meaning rather than just matching keywords.

How to use Context Lens?

To use Context Lens, set it up as a Model Context Protocol (MCP) server and point it to your content, such as codebases or documentation. You can then ask questions about the content, and it will provide relevant answers based on semantic understanding.

Key features of Context Lens?

  • Semantic search capabilities that understand meaning, not just keywords.
  • Zero setup required; it runs locally without the need for external databases or API keys.
  • Built-in serverless storage using LanceDB, ensuring data privacy.
  • Smart parsing and chunking of content for better search results.

Use cases of Context Lens?

  1. Analyzing codebases to understand functionality and dependencies.
  2. Searching through documentation to find relevant information quickly.
  3. Learning from open-source projects by querying their structure and features.

FAQ from Context Lens?

  • How does Context Lens compare to traditional keyword search?
    Context Lens provides semantic understanding, allowing it to return relevant results even if the exact keywords are not present.
  • Is there any cost associated with using Context Lens?
    No, Context Lens is completely free and runs locally without any subscriptions or API keys required.
  • Can I use Context Lens with private code?
    Yes, all processing happens locally, ensuring your data remains private.

Server Config

{
  "mcpServers": {
    "context-lens": {
      "command": "uvx",
      "args": [
        "context-lens"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
cornelcroi
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago