Octocode MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| githubSearchCodeA | Search GitHub code [EXTERNAL: GitHub API] |
| githubGetFileContentA | Read GitHub file or download directory [EXTERNAL: GitHub API] |
| githubViewRepoStructureA | Display GitHub repo structure [EXTERNAL: GitHub API] |
| githubSearchRepositoriesA | Search GitHub repositories [EXTERNAL: GitHub API] |
| githubSearchPullRequestsA | Search GitHub Pull Requests [EXTERNAL: GitHub API] |
| localSearchCodeA | Search code patterns [LOCAL: ripgrep] - START HERE for code questionsWithout LSP:
|
| localViewStructureA | View directory structure [LOCAL: filesystem] |
| localFindFilesA | Find files by metadata [LOCAL: filesystem]Config/docs: localGetFileContent directly
|
| localGetFileContentA | Read file content [LOCAL: filesystem] |
| lspGotoDefinitionA | Navigate to symbol definition [LOCAL: LSP]REQUIRES lineHint - call localSearchCode FIRST to get line number |
| lspFindReferencesA | Find all usages of a symbol [LOCAL: LSP]REQUIRES lineHint - call localSearchCode FIRST to get line number |
| lspCallHierarchyA | Trace function call relationships [LOCAL: LSP]REQUIRES lineHint - call localSearchCode FIRST to get line number |
| packageSearchA | Find NPM/Python packages [EXTERNAL: npm/PyPI] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-project | Interactive agent for scaffolding and generating new projects with architectural guidance and best practices, leveraging Octocode for research and feature implementation |
| help | Complete guide to all available Octocode prompts and tools for users |
| plan | Research-backed planning for bug fixes, features, or large refactors |
| research | Investigate anything using Octocode research tools |
| research_local | Investigate anything using Octocode research tools on local files (grep, ls, read, metadata) |
| review_pull_request | Comprehensive Pull Request review using Octocode tools with a Defects-First & Simplicity mental model |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct operation: GitHub tools for remote repo actions (get file, search code, search PRs, search repos, view structure), local tools for filesystem actions (find files, get file content, search code, view structure), LSP tools for semantic analysis (goto definition, find references, call hierarchy), and a separate package search tool. There is no overlap in purpose.
All tool names follow a consistent camelCase pattern with a prefix indicating domain (github, local, lsp) followed by a verb-noun combination (e.g., githubGetFileContent, localSearchCode, lspGotoDefinition). The naming is predictable and intuitive.
13 tools is well-scoped for a server that combines GitHub API exploration (5 tools), local filesystem analysis (4 tools), LSP-based code navigation (3 tools), and package search (1 tool). Each tool serves a clear purpose and contributes to the overall functionality without bloat.
The tool set covers the complete lifecycle for code exploration and analysis: discovery (search repos, view structure, find files), content access (get file content, search code), semantic navigation (goto definition, find references, call hierarchy), and package lookup. There are no obvious gaps for the server's stated purpose.