octocode-mcp and codebaxing
These are competitors offering overlapping functionality—both provide MCP-based semantic code search and indexing—though octocode-mcp emphasizes real-time multi-repository search across public and private codebases while codebaxing focuses on local-first indexing.
About octocode-mcp
bgauryy/octocode-mcp
MCP server for semantic code research and context generation on real-time using LLM patterns | Search naturally across public & private repos based on your permissions | Transform any accessible codebase/s into AI-optimized knowledge on simple and complex flows | Find real implementations and live docs from anywhere
Implements MCP (Model Context Protocol) with LSP-powered code intelligence (Go to Definition, Find References, Call Hierarchy) across GitHub, GitLab, and local codebases, enabling compiler-level understanding without parsing. Provides modular Agent Skills—including multi-phase research with session persistence, AST-driven code analysis, dependency graphing, and PR review across seven domains—composable via CLI or direct integration into Claude/Cursor.
About codebaxing
duysolo/codebaxing
Local codebase indexing and semantic code search via MCP
Parses code with Tree-sitter to extract symbols, embeds them using local or cloud models (Gemini/OpenAI/Voyage), and stores vectors in ChromaDB for semantic similarity search via MCP protocol. Integrates directly with Claude Desktop, Cursor, and Windsurf through automatic MCP server installation, enabling natural-language code queries within AI editors. Supports 28 languages with configurable embedding backends—local mode (free, ~200 texts/sec) or cloud providers (~10,000 texts/sec, including free Gemini tier).
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work