octocode-mcp MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

octocode.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

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

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

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

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

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

context_servers에 추가. 저장 시 Zed가 핫 리로드.

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

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: octocode-mcp

How to find real implementation patterns across repos with Octocode

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

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

사전 조건

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

흐름

Search for implementations

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

→ 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.✓ 복사됨

→ 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.✓ 복사됨

→ Production-ready code following verified patterns

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

함정

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

함께 쓰기: github · filesystem

Review a PR with full codebase context using Octocode

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

언제 쓸까: A PR touches a function you're not familiar with, and you need to understand all callers before approving.

흐름

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?✓ 복사됨

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

Does this signature change break any of those callers? Check the types.✓ 복사됨

→ 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.✓ 복사됨

→ Specific, line-level comments ready to post

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

함정

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

함께 쓰기: github

Onboard to an unfamiliar codebase in 30 minutes

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

언제 쓸까: Day one on a new repo — you need the architecture in your head, fast.

흐름

Get the high-level map

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

→ 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.✓ 복사됨

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

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

→ Conventions list with code examples

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

함정

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

함께 쓰기: filesystem

조합

다른 MCP와 조합해 10배 효율

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.✓ 복사됨

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.✓ 복사됨

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.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
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

비용 및 제한

운영 비용

API 쿼터: Inherits GitHub API limits: 5000 req/h for PAT, 30/min for code search. LSP calls are local and free.
호출당 토큰: 200-2000 tokens per tool response; large call hierarchies can hit 5k
금액: Free and open-source (MIT). You pay for your GitHub API usage and Claude tokens.
팁: Use local tools (browse_directory, search_local) when possible — they're free and fast. Save GitHub API calls for cross-repo searches.

보안

권한, 시크릿, 파급범위

최소 스코프: repo:read (GitHub PAT)

자격 증명 저장: GitHub PAT in environment variable. Configured during octocode-cli wizard.

데이터 외부 송신: GitHub/GitLab API for remote searches. LSP and local tools stay on your machine.

절대 부여 금지: 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.

문제 해결

자주 발생하는 오류와 해결

GitHub authentication failed

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

확인: 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

확인: 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

확인: node --version

대안

octocode-mcp 다른 것과 비교

대안	언제 쓰나	단점/장점
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

octocode-mcp