octocode-mcp MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Semantic code search across public and private GitHub/GitLab repos
LSP integration: go-to-definition, find-references, call hierarchy
Local codebase tools: directory browsing, file discovery, pattern search
9 built-in skills (Researcher, Engineer, PR Reviewer, RFC Generator, etc.)
Interactive CLI wizard for easy setup across editors

Live-Demo

In der Praxis

octocode.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "octocode",
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "octocode": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "octocode-mcp"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: octocode-mcp

How to find real implementation patterns across repos with Octocode

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

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

Voraussetzungen

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

Ablauf

Search for implementations

Search across popular TypeScript repos for real implementations of rate limiting middleware. Show me the top 3 most-starred examples.✓ Kopiert

→ Code snippets from real repos with file paths and context
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.✓ Kopiert

→ Full call chain from entry point to implementation
Adapt for your project

Based on that pattern, write a rate limiter for my Express app that uses Redis. Follow the same structure.✓ Kopiert

→ Production-ready code following verified patterns

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

Fallstricke

Searching too broadly returns noise — Scope to specific orgs or repos, and filter by language

Kombinieren mit: github · filesystem

Review a PR with full codebase context using Octocode

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

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

Ablauf

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?✓ Kopiert

→ Complete list of callers with context on criticality
Check for breaking changes

Does this signature change break any of those callers? Check the types.✓ Kopiert

→ Specific yes/no per caller with type analysis
Generate review comments

Draft 3 review comments: one about the breaking risk, one about test coverage, one about the naming choice.✓ Kopiert

→ Specific, line-level comments ready to post

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

Fallstricke

LSP not initialized for the language — Ensure the relevant language server is installed locally (e.g., tsserver for TypeScript)

Kombinieren mit: github

Onboard to an unfamiliar codebase in 30 minutes

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

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

Ablauf

Get the high-level map

Use Octocode to analyze this repo's structure. What are the main modules, entry points, and data flow?✓ Kopiert

→ Architecture overview with module boundaries
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.✓ Kopiert

→ End-to-end call chain with file locations
Identify conventions

What patterns does this codebase use? Error handling style, logging, dependency injection, test structure.✓ Kopiert

→ Conventions list with code examples

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

Fallstricke

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

Kombinieren mit: filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Kosten & Limits

Was der Betrieb kostet

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

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: repo:read (GitHub PAT)

Credential-Speicherung: GitHub PAT in environment variable. Configured during octocode-cli wizard.

Datenabfluss: GitHub/GitLab API for remote searches. LSP and local tools stay on your machine.

Niemals gewähren: repo:write admin:org

Octocode searches respect your GitHub token's permissions — it can see anything your token can see, including private repos.
Don't use a token with org-wide access unless you intend to search across the org.

Fehlerbehebung

Häufige Fehler und Lösungen

GitHub authentication failed

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

Prüfen: 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

Prüfen: 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

Prüfen: node --version

Alternativen

octocode-mcp vs. andere

Alternative	Wann stattdessen	Kompromiss
GitHub MCP (official)	You only need basic code search and PR/issue management, not LSP intelligence	No go-to-definition, no call hierarchy, no local codebase tools
Sourcegraph	You need enterprise-grade code intelligence with a web UI	Not MCP-native; heavier setup; paid for private repos

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen