Key takeaways
- MCP server with 14 tools for semantic code research — 6 GitHub tools, 4 local-codebase tools, 3 LSP navigation tools, and package-to-source resolution for npm and PyPI
- Actively shipping: npm hit v15.0.2 on June 6, 2026, and the repo was pushed the same day. ~16k npm downloads per month as of June 2026
- 863 stars, MIT license, TypeScript. Free and open source — no paid tier. Bridges the gap between lightweight search and full knowledge graphs
- Searches public and private GitHub repos based on your existing permissions. No separate indexing step required. GitLab support is no longer featured in current docs
FAQ
What is Octocode MCP?
An MCP server with 14 tools for AI agents to perform semantic code research across GitHub and local codebases. Includes LSP semantic navigation (definitions, references, call hierarchy), code search, PR archaeology, and npm/PyPI package-to-source discovery.
How does it compare to GitNexus?
GitNexus builds a full knowledge graph (deeper structural understanding). Octocode provides broader search across multiple repos without requiring an indexing step. Different trade-offs.
Is Octocode MCP free?
Yes. It is MIT-licensed open source distributed via npm, with no paid tier or enterprise pricing as of June 2026.
Overview
Octocode MCP is a code research MCP server that gives AI agents deep access to GitHub and local codebases through 14 specialized tools: six GitHub tools (code/repo/PR search, file content, repo structure, cloning), four local tools (ripgrep-backed search, file discovery), three LSP tools (go-to-definition, find-references, call hierarchy), and npm/PyPI package-to-source resolution. It searches public and private repos based on your existing permissions, with no separate indexing step.
Key stats (as of June 2026): 863 stars, 73 forks, MIT license, TypeScript. ~16,000 npm downloads in the past month. Created June 2025.
Status: actively developed. The repo was pushed June 6, 2026, the same day npm version 15.0.2 shipped. Note the release cadence moved to npm — GitHub Releases stop at 9.1.1 (December 2025), but versions 10–15 kept landing on npm through June 2026. Current docs also reference a companion octocode CLI.
Pricing: free, open source, no paid tier or enterprise offering as of June 2026.
Competitive Position
Strengths: Among the most tool-rich MCP code search servers (14 tools). Covers remote GitHub + local codebases in one server. No indexing required. PR archaeology and LSP call-hierarchy tools are rare in this category.
Weaknesses: No knowledge graph — cannot do blast radius analysis. Smaller community than the big coding-agent projects. Depends on GitHub API rate limits.
Cautions
- GitLab support quietly dropped from the docs — earlier marketing listed GitLab; the current README covers only GitHub, local, LSP, and package tools. Treat cross-platform claims as GitHub-only until documented otherwise
- Rapid major-version churn — v6 to v15 in nine months means breaking changes are routine; pin versions
- Release notes lag — GitHub Releases stopped at 9.1.1 while npm moved on to 15.x, so changelog archaeology requires reading commits
What Developers Say
The November 2025 Hacker News launch thread was warmly received. Danaharel wrote: "we've recently integrated Octocode MCP as part of an internal AI assistant, built for Product Managers to explore product logic directly from the codebase. It's been incredibly useful for bridging the gap between product and engineering - especially with the semantic code search and multi-repo context handling." CodeDeficient called it "an essential tools for solo developers and production teams alike. Its ability to connect AI agents to GitHub is unmatched in quality and results... Absolutely love this tool and would recommend to anyone, any day." IsraelZ added: "it changed my and my team workflow and velocity." No substantial critical reviews surfaced as of June 2026.
Bottom Line
Recommended for: teams whose agents need to research code across many GitHub repos (public or private) without standing up an indexing pipeline, and anyone wanting LSP-grade navigation plus PR history in a single free MCP server.
Not recommended for: teams needing GitLab/Bitbucket coverage (no longer documented), blast-radius/impact analysis (use a knowledge-graph tool like GitNexus), or version stability without pinning.
Outlook: healthy. Stars grew from 751 to 863 since March 2026, npm sits at ~16k monthly downloads, and the maintainer is shipping weekly. The main risks are single-maintainer bus factor and GitHub API dependence.
Research by Ry Walker Research