Octocode MCP

## Search GitHub code [EXTERNAL: GitHub API] <when> - Find code patterns | Locate files by path - match="file" -> content | match="path" -> file names - External research | Cross-repo patterns </when> <fromTool> - githubSearchRepositories: After finding repo - githubViewRepoStructure: After understanding layout - packageSearch: After finding package - self: Refine query | Switch match=file<->path </fromTool> <toTool> - githubGetFileContent: Read matched files (text_matches for matchString) - githubViewRepoStructure: Explore around matches - githubSearchPullRequests: Find history </toTool> <gotchas> - 1-2 filters safe. NEVER combine extension+filename+path - path is strict prefix: "pkg" finds pkg/file, NOT parent/pkg/file - Start lean: single filter -> verify -> add filters - Prefer owner+repo for precision - For packages: packageSearch first </gotchas> <examples> - owner="facebook", repo="react", match="path", keywordsToSearch=["utils"] - keywordsToSearch=["useState"], match="file" - path="src/api", extension="ts", keywordsToSearch=["export"] </examples>

## Read GitHub file content [EXTERNAL: GitHub API] <when> - Read file from known path (after discovery/search) - External library implementation research - Read configs, docs, or source from GitHub repos </when> <fromTool> - githubSearchCode: Read from results (use text_matches for matchString) - githubViewRepoStructure: Read discovered paths - packageSearch: Read package source - self: Expand context </fromTool> <toTool> - githubSearchCode: Search imports/patterns - githubSearchPullRequests: Find file history - packageSearch: Look up imports </toTool> <gotchas> - Choose ONE: matchString OR startLine+endLine OR fullContent - Large files: Use matchString for token efficiency - 300KB max (FILE_TOO_LARGE error) - Branch: Use NAME (e.g., "main"), not SHA </gotchas> <examples> - matchString="export function", matchStringContextLines=20 - startLine=1, endLine=50 - fullContent=true (small configs only) </examples>

## Display GitHub repo structure [EXTERNAL: GitHub API] <when> - Understand layout | Discover paths | Entry point - Workflow: Root (depth=1) -> Drill (path+depth=2) -> Search/Read </when> <fromTool> - githubSearchRepositories: After finding repo - packageSearch: After finding package - self: Drill into subdirectory </fromTool> <toTool> - githubSearchCode: Search in discovered dirs - githubGetFileContent: Read discovered files - githubSearchPullRequests: Find changes </toTool> <gotchas> - Start at root (path="", depth=1) first - depth=2 slow on large dirs - use on subdirs - Monorepos: Check packages/, apps/, libs/ - Auto-filters noisy dirs (.git, node_modules, dist) - Max 200 items - check summary.truncated </gotchas> <examples> - path="", depth=1 (root) - path="src", depth=2 (drill into source) - path="packages/core", depth=1 (monorepo) </examples>

## Search GitHub repositories [EXTERNAL: GitHub API] <when> - External research | Finding repos | Discovering projects - Keywords for org repos, topics for open-source - Known packages: use packageSearch first (faster) </when> <fromTool> - packageSearch: After finding package, explore repo - githubSearchCode: Found code? Find origin repo - self: Refine query | Switch topics<->keywords </fromTool> <toTool> - githubViewRepoStructure: Explore structure - githubSearchCode: Search code - githubGetFileContent: Read files - githubSearchPullRequests: Find changes </toTool> <gotchas> - Check pushedAt (code change) > updatedAt (meta change) - stars >1000 filters noise (may hide new projects) - Try synonyms: auth<->authentication, plugin<->extension - Archived repos auto-excluded </gotchas> <examples> - topicsToSearch=["typescript", "cli"], stars=">1000" - owner="wix-private", keywordsToSearch=["auth-service"] </examples>

## Search GitHub Pull Requests [EXTERNAL: GitHub API] <when> - Code archaeology: WHY was code written this way? - Implementation history | Review changes | Find introducing PR - Workflow: type=metadata first -> type=partialContent for files </when> <fromTool> - githubSearchCode: Found code? Find PRs that changed it - githubGetFileContent: Found file? Find change history - self: Refine query | Widen date range </fromTool> <toTool> - githubGetFileContent: Read current state - githubSearchCode: Search patterns from patches - self: Deep dive with prNumber + type=partialContent </toTool> <gotchas> - prNumber ignores ALL other filters - type=metadata first (fast), then partialContent - Avoid fullContent on large PRs (token expensive) - withComments=true for understanding WHY </gotchas> <examples> - prNumber=123, type="metadata" - owner="org", repo="repo", state="closed", merged=true - prNumber=123, type="partialContent", partialContentMetadata=[{"file": "src/app.ts"}] </examples>

Interactive agent for scaffolding and generating new projects with architectural guidance and best practices, leveraging Octocode for research and feature implementation

Complete guide to all available Octocode prompts and tools for users

Initialize Octocode context by gathering user requirements and preferences

Research-backed planning for bug fixes, features, or large refactors

Investigate anything using Octocode research tools