Sourcerer Mcp

Created By
st3v3nmw10 months ago
An MCP server for semantic code search & navigation that helps AI agents work efficiently without burning through costly tokens. Instead of reading entire files, agents can search conceptually and jump directly to the specific functions, classes, and code chunks they need.
Overview

what is Sourcerer MCP?

Sourcerer MCP is a server designed for semantic code search and navigation, enabling AI agents to efficiently locate specific functions, classes, and code chunks without the need to read entire files, thus conserving costly token usage.

how to use Sourcerer MCP?

To use Sourcerer MCP, install it via Go or Homebrew, configure it with your OpenAI API key, and set up your project workspace. Once configured, you can utilize its semantic search capabilities to find relevant code snippets.

key features of Sourcerer MCP?

  • Semantic search index for efficient code navigation
  • Integration with OpenAI API for generating embeddings
  • Automatic re-indexing of changed files
  • Support for multiple programming languages (Go, with plans for Python, TypeScript, JavaScript)

use cases of Sourcerer MCP?

  1. Assisting AI agents in quickly finding relevant code snippets.
  2. Reducing cognitive load by allowing conceptual searches instead of text matching.
  3. Enhancing code navigation in large codebases.

FAQ from Sourcerer MCP?

  • What programming languages does Sourcerer MCP support?

Currently, it supports Go, with plans to add Python, TypeScript, and JavaScript.

  • Do I need an OpenAI API key to use Sourcerer MCP?

Yes, an OpenAI API key is required for generating embeddings.

  • How does Sourcerer MCP handle file changes?

It automatically re-indexes changed files and respects .gitignore files.

Server Config

{
  "mcpServers": {
    "sourcerer": {
      "command": "sourcerer",
      "env": {
        "OPENAI_API_KEY": "your-openai-api-key",
        "SOURCERER_WORKSPACE_ROOT": "/path/to/your/project"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
9 months ago
Author Name
st3v3nmw
Star
-
Language
-
License
-
Category

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)

a day ago