/ Diretório / Playground / octocode-mcp
● Comunidade bgauryy ⚡ Instantâneo

octocode-mcp

por bgauryy · bgauryy/octocode-mcp

Semantic code research MCP — search across public and private repos using natural language, with LSP-powered go-to-definition and call hierarchy.

Octocode is an MCP server that gives your AI assistant senior-engineer-level code research skills. It combines GitHub and GitLab integration with local LSP intelligence (go-to-definition, find-references, call hierarchy) to search, understand, and generate context from any accessible codebase. Comes with 9 specialized skills for research, PR review, RFC generation, and more.

Por que usar

Principais recursos

Demo ao vivo

Como fica na prática

octocode.replay ▶ pronto
0/0

Instalar

Escolha seu cliente

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "octocode",
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ]
    }
  ]
}

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json
{
  "context_servers": {
    "octocode": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "octocode-mcp"
        ]
      }
    }
  }
}

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

claude mcp add octocode -- npx -y octocode-mcp

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: octocode-mcp

How to find real implementation patterns across repos with Octocode

👤 Developers looking for how others solved a specific problem ⏱ ~20 min intermediate

Quando usar: You need to implement something (auth, caching, rate limiting) and want to see how real codebases do it, not just docs.

Pré-requisitos
  • Octocode MCP installed — npx octocode-cli (interactive wizard) or add octocode-mcp to your MCP config
  • GitHub authentication — Follow the authentication setup guide in the repo docs
Fluxo
  1. Search for implementations
    Search across popular TypeScript repos for real implementations of rate limiting middleware. Show me the top 3 most-starred examples.✓ Copiado
    → Code snippets from real repos with file paths and context
  2. Drill into the best one
    For the best example, use go-to-definition to trace how the rate limiter is configured and where it's applied in the middleware chain.✓ Copiado
    → Full call chain from entry point to implementation
  3. Adapt for your project
    Based on that pattern, write a rate limiter for my Express app that uses Redis. Follow the same structure.✓ Copiado
    → Production-ready code following verified patterns

Resultado: A well-researched implementation based on real-world patterns, not hallucinated API calls.

Armadilhas
  • Searching too broadly returns noise — Scope to specific orgs or repos, and filter by language
Combine com: github · filesystem

Review a PR with full codebase context using Octocode

👤 Code reviewers who need to understand impact beyond the diff ⏱ ~15 min intermediate

Quando usar: A PR touches a function you're not familiar with, and you need to understand all callers before approving.

Fluxo
  1. Analyze the changed function
    Use Octocode's find-references to show me every caller of the function modified in PR #42. Are any of them in hot paths?✓ Copiado
    → Complete list of callers with context on criticality
  2. Check for breaking changes
    Does this signature change break any of those callers? Check the types.✓ Copiado
    → Specific yes/no per caller with type analysis
  3. Generate review comments
    Draft 3 review comments: one about the breaking risk, one about test coverage, one about the naming choice.✓ Copiado
    → Specific, line-level comments ready to post

Resultado: A thorough PR review grounded in actual usage data, not guesswork.

Armadilhas
  • LSP not initialized for the language — Ensure the relevant language server is installed locally (e.g., tsserver for TypeScript)
Combine com: github

Onboard to an unfamiliar codebase in 30 minutes

👤 New team members or contractors ramping on a project ⏱ ~30 min beginner

Quando usar: Day one on a new repo — you need the architecture in your head, fast.

Fluxo
  1. Get the high-level map
    Use Octocode to analyze this repo's structure. What are the main modules, entry points, and data flow?✓ Copiado
    → Architecture overview with module boundaries
  2. Trace a key flow
    Trace the request flow from the API handler for POST /users to the database layer. Show me every function in the chain.✓ Copiado
    → End-to-end call chain with file locations
  3. Identify conventions
    What patterns does this codebase use? Error handling style, logging, dependency injection, test structure.✓ Copiado
    → Conventions list with code examples

Resultado: A mental model of the codebase architecture, key flows, and conventions — enough to start contributing.

Armadilhas
  • Repo too large for a single analysis pass — Start with one module (e.g., 'just the API layer') and expand
Combine com: filesystem

Combinações

Combine com outros MCPs para 10× de alavancagem

octocode + github

Octocode finds the pattern across repos, GitHub MCP creates the PR implementing it

Use Octocode to find how other repos handle JWT refresh tokens, then use GitHub MCP to create a PR implementing the best pattern in our repo.✓ Copiado
octocode + filesystem

Octocode analyzes remote repos for patterns, filesystem MCP applies them to your local codebase

Research how nf-core handles CI configuration via Octocode, then write a similar .github/workflows/ci.yml for my project.✓ Copiado
octocode + sentry

Sentry identifies the error, Octocode traces all callers to assess blast radius

Sentry shows an error in parseConfig(). Use Octocode to find all callers of parseConfig and assess which user flows are affected.✓ Copiado

Ferramentas

O que este MCP expõe

FerramentaEntradasQuando chamarCusto
search_code query: str, org?: str, repo?: str, language?: str Find code patterns across repos using natural language 1 GitHub API call
go_to_definition file: str, line: int, symbol: str Jump to where a function/class/type is defined Local LSP call
find_references file: str, line: int, symbol: str Find all callers of a function or users of a type Local LSP call
call_hierarchy file: str, line: int, symbol: str Understand the full call chain around a function Local LSP call
browse_directory path: str Explore repo structure Local file read
search_local query: str, path?: str Grep-like search in a local codebase Local file scan

Custo e limites

O que custa rodar

Cota de API
Inherits GitHub API limits: 5000 req/h for PAT, 30/min for code search. LSP calls are local and free.
Tokens por chamada
200-2000 tokens per tool response; large call hierarchies can hit 5k
Monetário
Free and open-source (MIT). You pay for your GitHub API usage and Claude tokens.
Dica
Use local tools (browse_directory, search_local) when possible — they're free and fast. Save GitHub API calls for cross-repo searches.

Segurança

Permissões, segredos, alcance

Escopos mínimos: repo:read (GitHub PAT)
Armazenamento de credenciais: GitHub PAT in environment variable. Configured during octocode-cli wizard.
Saída de dados: GitHub/GitLab API for remote searches. LSP and local tools stay on your machine.
Nunca conceda: repo:write admin:org

Solução de problemas

Erros comuns e correções

GitHub authentication failed

Re-run npx octocode-cli to reconfigure auth, or manually set your GitHub PAT in the environment

Verificar: curl -H 'Authorization: Bearer $GITHUB_TOKEN' https://api.github.com/user
LSP features (go-to-definition) not working

Ensure the relevant language server is installed: tsserver for TypeScript, pyright/pylsp for Python, gopls for Go

Verificar: Check that the language server binary is on your PATH
Search returns no results for private repos

Your GitHub PAT needs repo:read scope and must include the specific repo in its access list (fine-grained PAT)

npx octocode-mcp hangs on startup

Check Node.js version (18+ required). Clear npx cache: npx clear-npx-cache

Verificar: node --version

Alternativas

octocode-mcp vs. outros

AlternativaQuando usarTroca
GitHub MCP (official)You only need basic code search and PR/issue management, not LSP intelligenceNo go-to-definition, no call hierarchy, no local codebase tools
SourcegraphYou need enterprise-grade code intelligence with a web UINot MCP-native; heavier setup; paid for private repos

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills