O

Octocode MCP - AI Context Platform Community

MCP server Β· by bgauryy

Developer Tools npm v7.0.9

AI code research platform. Search, analyze, and extract insights from any GitHub repository.

View source β†— Generate config for multiple servers More servers

Install

registry version 7.0.9

npm
npx -y octocode-mcp

Setup by client

Pick your client β€” the config below is generated for this server (local stdio). Copy respects the β€œPin version” switch above.

claude_desktop_config.json

{
  "mcpServers": {
    "octocode": {
      "command": "npx",
      "args": [
        "-y",
        "octocode-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
      }
    }
  }
}

Format verified against the official Claude Desktop docs β†—.

Environment variables

Defined in the server's official registry manifest. Required secrets are shown as <YOUR_…> placeholders in the configs above.

  • GITHUB_TOKEN secret β€” GitHub Personal Access Token. Optional - authenticate via GitHub CLI (gh auth login) for automatic token management, or set this token manually for CI/CD environments.

Implementation status

Community implementation

Octocode has not published an official MCP server as of 2026-10-15. This page lists the most popular community implementation.

Evidence β†—

Last verified: 2026-10-15 ｜ Sources: Verification basis β†—

GitHub

⭐ 950 stars Β· ζœ€θΏ‘ζ›΄ζ–°δΊŽ 14 倩前 Β· MIT license

About this server

Octocode: agentic research platform > > > Evidence-first code research for AI agents and developers. Octocode researches your local code and external code alike (GitHub repositories, PRs, npm) with one toolset: ripgrep + AST search, trees, precise reads, and LSP. Use it as a CLI or MCP server , backed by a Rust engine for fast, token-efficient results across single files or mega-repos. --- Table of contents Quick start Why Octocode Built for research (benchmarks) Tools MCP CLI Configuration Authentication methods Security Language support Skills Architecture Documentation Troubleshooting Agent workflows --- Quick start Prerequisites: Node.js 20.12+ Run the Octocode CLI with npx Authenticate with GitHub - optional, but unlocks private repositories and higher API rate limits: Choose your interface. Same tools and Rust engine on both. (Clone is on by default in the CLI, opt-in for MCP.) πŸ–₯️ CLI - research straight from your terminal: πŸ€– MCP - one-click install: > > > > >Show more install options (Windsurf, Kiro, Goose, LM Studio, Claude Code) > > > > > > > > Claude Code: > Any other client: npx octocode install --- Use it as an MCP server Add to your MCP client config (or use a one-click install above): Put a GitHub token and options under env (see Configuration). Use it as an agentic-friendly CLI Run npx octocode and agents figure out the rest. The bare command prints built-in usage and the full tool catalog, so any coding agent knows how to drive it out of the box, no MCP client or extra wiring required. Every MCP tool is also a plain command: JSON in, token-efficient YAML out. Local paths route to local tools; owner/repo[/path] routes to GitHub. Learn more at octocode.ai . --- Why Octocode Agents code better from evidence than from guesses. Octocode researches two worlds with one flow , your local code and external code on GitHub and npm, and hands back compact, citable context before an agent changes, reviews, or explains code. Code is truth; context is the map. Most tools do one slice (web search, or grep your repository) and hand back a fixed blob. Octocode covers the whole loop and lets the agent decide what data it needs next : Agent-driven, efficient flows. Instead of one-shot dumps, Octocode chains cheap steps into an optimized research flow: broad code search, then fetch only the exact matched lines/region , with smart pagination and out-of-the-box minification so the model never over-fetches. Every result carries next-step hints to the cheapest follow-up. Scales to monorepos. Spot a pattern in one repository, follow the PR that introduced it, then trace it across other repositories and your own files, without leaving the chat. Clone any repository and study it locally. Smart GitHub flow. Parallel bulk queries across code, PRs, commits, issues, and repositories, all with the same search-broad, read-narrow, trace-semantically discipline. Works without GitHub. Clone any repository and point the local tools (search, AST, LSP, content) at it, same evidence-first flow. Reads shape, not noise. On-the-fly minify/skeletonize across 70+ languages: a 100 KB file in a few hundred tokens, not walls of boilerplate. Fast, self-contained. Search, parsing, navigation, and redaction run in one prebuilt Rust engine : quick on a laptop or a mega-repo, nothing extra to install. Safe by default. Every byte to the model is scanned and secrets redacted first (see Security). What you can do (whenever the next step needs proven context, not a guess): Need Use Octocode to ------ ----------------- Codebase questions Search local or GitHub code, read exact regions, browse trees, and carry file/line anchors into the answer. Implementation research Compare patterns across repositories, npm packages, pull requests, commits, and local files before changing code. Semantic navigation Resolve definitions, references, callers/callees, call hierarchy, hovers, symbols, diagnostics, and type relationships through LSP. Structural matching Run AST-shaped searches with patterns or YAML rules so comments and strings do not become false positives. Large-file context Minify, skeletonize, or paginate code so agents spend tokens on relevant structure instead of boilerplate. Agent workflows Same engine through MCP, CLI, and Agent Skills. --- Built for research (benchmarks) A blind, head-to-head test on research-oriented flows rather than plain lookups (multi-hop traces, dependency/call-graph chains, commit ranges, blast-radius, PR reviews across repositories). How it works: 30 GitHub questions Γ— 3 passes; Octocode vs gh , gh +Headroom, and gh +RTK on identical questions (only the CLI differs). A blind judge (gpt-5.5) grades correctness; the metric is characters through the model , counted from instrumented logs (characters, not tokens). Result: at near-parity correctness, Octocode answers with 2.0Γ— fewer characters than plain gh , 2.6Γ— fewer than gh +Headroom, and 3.2Γ— fewer than gh +RTK in the local-build headline runs. β–Ά Open the interactive report Β· run it / method Β· questions Β· all reports --- Tools 17 tools in the full catalog. How many register depends on the surface and the flags you set: Surface Registers What that set is --- ---: --- MCP, no flags 8 GitHub search and read, plus npmSearch MCP, ENABLE LOCAL=true 14 Adds the five local tools and lspGetSemantics MCP, + ENABLE CLONE=true 15 Adds ghCloneRepo MCP, + ENABLE TOOLS allowlist 17 Adds ghListReleases and ghSearchDiscussions CLI, no flags 15 Local tools and clone are on by default CLI, + ENABLE RELEASES=1 ENABLE DISCUSSIONS=1 17 Adds the same two GitHub tools ghListReleases and ghSearchDiscussions need two settings on MCP, not one: ENABLE RELEASES=1 or ENABLE DISCUSSIONS=1 puts the tool in the catalog, and ENABLE TOOLS="ghListReleases,ghSearchDiscussions" registers it. Either setting alone leaves the tool unregistered, because both carry isDefault: false and the MCP registration filter admits only default or explicitly allowlisted tools. The CLI needs only the ENABLE RELEASES and ENABLE DISCUSSIONS flags. ENABLE LOCAL and ENABLE CLONE accept true or 1 ; ENABLE RELEASES and ENABLE DISCUSSIONS also accept yes and on . Flags: Configuration. Token knobs. concise:true returns path/title-only lists. minify controls file read density: symbols = skeleton with line numbers, standard = comments/blanks stripped (default), none = exact bytes. GitHub tools Tool What it does Knob ------ -------------- ------ ghSearchCode Code and path search across GitHub by owner, repository, path, filename, extension, and match filters. Accepts 1 to 5 parallel queries. concise ghGetFileContent Read a GitHub file or region: full file, line range, match slice, or paginated chars. minify ghViewRepoStructure Browse a repository's directory tree, plus opt-in repository enrichments. include ghSearchRepos Discover repositories by keywords, owner, topic, language, stars, updated, license, visibility. concise ghSearchPullRequests Search pull requests, or deep-read one PR: files, patches, comments, reviews, commits. content ghSearchIssues Search issues, or read one issue's body and comments. content ghSearchCommits Walk a repository's commit history, or compare two refs ( base + head ). includeDiff ghListReleases List releases and the latest stable release, with opt-in assets. Opt-in (see Tools for the flags). includeAssets ghSearchDiscussions Search a repository's Discussions (Q&A, RFCs, announcements) through GraphQL. Opt-in (see Tools for the flags). keywordsToSearch ghCloneRepo Clone a repository or sparse subtree into the local cache for local and LSP analysis. Opt-in on MCP ( ENABLE CLONE=true ); on by default in the CLI. sparsePath Local tools Tool What it does Knob ------ -------------- ------ localSearchCode Local code/text search returning file and line anchors. mode:"structural" runs Octocode AST shape queries ( pattern or rule ). mode localViewStructure Browse a local directory tree: depth, filters, pagination, metadata. detail localFindFiles Find local files and directories by name, path, regex, extension, size, time, permissions, type. localFindDeadCode Find likely-unreferenced exports and dead-code clusters using whole-repository reachability analysis. entrypoints localGetFileContent Read a local file or region: exact slice, match string, line range, or paginated chars. minify Package search Tool What it does Knob ------ -------------- ------ npmSearch npm package lookup and keyword search; returns metadata and the source repository for GitHub handoff. concise LSP Tool What it does ------ -------------- lspGetSemantics Typed semantic navigation: definition , references , callers , callees , callHierarchy , hover , documentSymbols , typeDefinition , implementation , workspaceSymbol , supertypes , subtypes , and diagnostic . From the CLI, invoke it directly: npx octocode tools lspGetSemantics --queries ' >' . Navigation runs through installed language servers (see the LSP tools reference). Full schemas, fields, and examples for every tool live in docs/OCTOCODE TOOLS.md (linked under Documentation). --- MCP The MCP server exposes the Octocode tool catalog directly to your AI assistant over stdio. Manual configuration Add to your MCP client config, using octocode-mcp : Add a GitHub token and options under env - see Authentication and Configuration. --- CLI Same research engine, no MCP client needed. Local paths route to local tools; owner/repo[/path] routes to GitHub. Authenticate once with npx octocode auth login (see Authentication); run npx octocode --help for full usage. Commands Tool commands Command What it does --------- -------------- npx octocode tools > --scheme Show one tool's schema: fields, types, bounds, defaults npx octocode tools > --queries ' >' Run a tool (same tools as MCP), YAML output npx octocode tools > --queries ' >' --json Run a tool, full CallToolResult JSON npx octocode tools List every available tool More commands Cache and clone β€” npx octocode clone , npx octocode cache fetch status clear Skills β€” npx octocode skill list install check info remove for bundled Octocode skills Language servers β€” npx octocode lsp-server list install status uninstall clean Setup and introspection β€” npx octocode install , npx octocode auth , npx octocode status , npx octocode context Full syntax, flags, and exit codes: Octocode CLI guide --- Configuration Everything is optional; Octocode runs on sensible defaults. Settings resolve from three sources, in priority order: MCP / environment variables (highest): per client or per project, set in your MCP config env or your shell. Global config : >/.octocoderc , machine-wide defaults read by both the CLI and the MCP server . Built-in defaults : used when neither is set. Octocode home ( > ) holds the global config, encrypted credentials, sessions, stats, and tmp materialization caches. On every platform it is .octocode inside the OS home directory β€” /.octocode on macOS and Linux, %USERPROFILE%\.octocode on Windows. Override it with OCTOCODE HOME . Set values as MCP env entries (per client; these win over .octocoderc ) or globally in >/.octocoderc (JSON with comments). Tokens never go in .octocoderc β€” use env or npx octocode auth login . Common settings Most-used settings (both CLI and MCP unless noted): Env var .octocoderc key Default What it does --------- ------------------- --------- -------------- OCTOCODE TOKEN / GH TOKEN / GITHUB TOKEN env only unset GitHub token, in priority order. Never in .octocoderc . ENABLE LOCAL local.enabled CLI true ; on MCP set it explicitly Local filesystem and LSP tools on or off. ENABLE CLONE local.enableClone CLI true , MCP false ghCloneRepo + directory fetch on/off. WORKSPACE ROOT local.workspaceRoot cwd Root for resolving relative local paths. ALLOWED PATHS local.allowedPaths [] Extra path allowlist for local access. OCTOCODE OUTPUT FORMAT output.format yaml Response format: yaml or json . OCTOCODE HOME , GitHub Enterprise ( GITHUB API URL ), MCP tool allowlisting ( TOOLS TO RUN / ENABLE TOOLS / DISABLE TOOLS ), and network timeouts/retries: see the Configuration Reference. Example configuration /.octocode/.octocoderc : Per-project overrides and custom LSP servers live in a workspace .octocode/ folder. For the full .octocoderc schema, a ready-to-copy example, clone-cache tuning, GitHub Enterprise setup, and precedence details, see the Configuration Reference. --- Authentication methods GitHub-backed tools require authentication. Any one method is enough. Full details: Authentication Setup. Option 1: Octocode CLI (recommended) Interactive login lets you choose Octocode browser OAuth or gh auth login . Octocode OAuth credentials are stored encrypted on disk. Option 2: GitHub CLI (also supported) Octocode reads the gh token automatically β€” no further config needed. Option 3: Personal access token (also supported) Set O…

Summary from the project README β€” github.com/bgauryy/octocode-mcp

Distributed as npm, listed under Developer Tools. Review our MCP security guide before granting access to real data.

Frequently asked questions

What does the Octocode MCP - AI Context Platform MCP server do?

Octocode: agentic research platform > > > Evidence-first code research for AI agents and developers. Octocode researches your local code and external code alike (GitHub repositories, PRs, npm) with one toolset: ripgrep + AST search, trees, precise reads, and LSP. Use it as a CLI or MCP server , backed by a Rust engine for fast, token-efficient results across single files or mega-repos. --- Table of contents Quick start Why Octocode Built for research (benchmarks) Tools MCP CLI Configuration Authentication methods Security Language support Skills Architecture Documentation Troubleshooting Agent workflows --- Quick start Prerequisites: Node.js 20.12+ Run the Octocode CLI with npx Authenticate with GitHub - optional, but unlocks private repositories and higher API rate limits: Choose your interface. Same tools and Rust engine on both. (Clone is on by default in the CLI, opt-in for MCP.) πŸ–₯️ CLI - research straight from your terminal: πŸ€– MCP - one-click install: > > > > >Show more install options (Windsurf, Kiro, Goose, LM Studio, Claude Code) > > > > > > > > Claude Code: > Any other client: npx octocode install --- Use it as an MCP server Add to your MCP client config (or use a one-click install above): Put a GitHub token and options under env (see Configuration). Use it as an agentic-friendly CLI Run npx octocode and agents figure out the rest. The bare command prints built-in usage and the full tool catalog, so any coding agent knows how to drive it out of the box, no MCP client or extra wiring required. Every MCP tool is also a plain command: JSON in, token-efficient YAML out. Local paths route to local tools; owner/repo[/path] routes to GitHub. Learn more at octocode.ai . --- Why Octocode Agents code better from evidence than from guesses. Octocode researches two worlds with one flow , your local code and external code on GitHub and npm, and hands back compact, citable context before an agent changes, reviews, or explains code. Code is truth; context is the map. Most tools do one slice (web search, or grep your repository) and hand back a fixed blob. Octocode covers the whole loop and lets the agent decide what data it needs next : Agent-driven, efficient flows. Instead of one-shot dumps, Octocode chains cheap steps into an optimized research flow: broad code search, then fetch only the exact matched lines/region , with smart pagination and out-of-the-box minification so the model never over-fetches. Every result carries next-step hints to the cheapest follow-up. Scales to monorepos. Spot a pattern in one repository, follow the PR that introduced it, then trace it across other repositories and your own files, without leaving the chat. Clone any repository and study it locally. Smart GitHub flow. Parallel bulk queries across code, PRs, commits, issues, and repositories, all with the same search-broad, read-narrow, trace-semantically discipline. Works without GitHub. Clone any repository and point the local tools (search, AST, LSP, content) at it, same evidence-first flow. Reads shape, not noise. On-the-fly minify/skeletonize across 70+ languages: a 100 KB file in a few hundred tokens, not walls of boilerplate. Fast, self-contained. Search, parsing, navigation, and redaction run in one prebuilt Rust engine : quick on a laptop or a mega-repo, nothing extra to install. Safe by default. Every byte to the model is scanned and secrets redacted first (see Security). What you can do (whenever the next step needs proven context, not a guess): Need Use Octocode to ------ ----------------- Codebase questions Search local or GitHub code, read exact regions, browse trees, and carry file/line anchors into the answer. Implementation research Compare patterns across repositories, npm packages, pull requests, commits, and local files before changing code. Semantic navigation Resolve definitions, references, callers/callees, call hierarchy, hovers, symbols, diagnostics, and type relationships through LSP. Structural matching Run AST-shaped searches with patterns or YAML rules so comments and strings do not become false positives. Large-file context Minify, skeletonize, or paginate code so agents spend tokens on relevant structure instead of boilerplate. Agent workflows Same engine through MCP, CLI, and Agent Skills. --- Built for research (benchmarks) A blind, head-to-head test on research-oriented flows rather than plain lookups (multi-hop traces, dependency/call-graph chains, commit ranges, blast-radius, PR reviews across repositories). How it works: 30 GitHub questions Γ— 3 passes; Octocode vs gh , gh +Headroom, and gh +RTK on identical questions (only the CLI differs). A blind judge (gpt-5.5) grades correctness; the metric is characters through the model , counted from instrumented logs (characters, not tokens). Result: at near-parity correctness, Octocode answers with 2.0Γ— fewer characters than plain gh , 2.6Γ— fewer than gh +Headroom, and 3.2Γ— fewer than gh +RTK in the local-build headline runs. β–Ά Open the interactive report Β· run it / method Β· questions Β· all reports --- Tools 17 tools in the full catalog. How many register depends on the surface and the flags you set: Surface Registers What that set is --- ---: --- MCP, no flags 8 GitHub search and read, plus npmSearch MCP, ENABLE LOCAL=true 14 Adds the five local tools and lspGetSemantics MCP, + ENABLE CLONE=true 15 Adds ghCloneRepo MCP, + ENABLE TOOLS allowlist 17 Adds ghListReleases and ghSearchDiscussions CLI, no flags 15 Local tools and clone are on by default CLI, + ENABLE RELEASES=1 ENABLE DISCUSSIONS=1 17 Adds the same two GitHub tools ghListReleases and ghSearchDiscussions need two settings on MCP, not one: ENABLE RELEASES=1 or ENABLE DISCUSSIONS=1 puts the tool in the catalog, and ENABLE TOOLS="ghListReleases,ghSearchDiscussions" registers it. Either setting alone leaves the tool unregistered, because both carry isDefault: false and the MCP registration filter admits only default or explicitly allowlisted tools. The CLI needs only the ENABLE RELEASES and ENABLE DISCUSSIONS flags. ENABLE LOCAL and ENABLE CLONE accept true or 1 ; ENABLE RELEASES and ENABLE DISCUSSIONS also accept yes and on . Flags: Configuration. Token knobs. concise:true returns path/title-only lists. minify controls file read density: symbols = skeleton with line numbers, standard = comments/blanks stripped (default), none = exact bytes. GitHub tools Tool What it does Knob ------ -------------- ------ ghSearchCode Code and path search across GitHub by owner, repository, path, filename, extension, and match filters. Accepts 1 to 5 parallel queries. concise ghGetFileContent Read a GitHub file or region: full file, line range, match slice, or paginated chars. minify ghViewRepoStructure Browse a repository's directory tree, plus opt-in repository enrichments. include ghSearchRepos Discover repositories by keywords, owner, topic, language, stars, updated, license, visibility. concise ghSearchPullRequests Search pull requests, or deep-read one PR: files, patches, comments, reviews, commits. content ghSearchIssues Search issues, or read one issue's body and comments. content ghSearchCommits Walk a repository's commit history, or compare two refs ( base + head ). includeDiff ghListReleases List releases and the latest stable release, with opt-in assets. Opt-in (see Tools for the flags). includeAssets ghSearchDiscussions Search a repository's Discussions (Q&A, RFCs, announcements) through GraphQL. Opt-in (see Tools for the flags). keywordsToSearch ghCloneRepo Clone a repository or sparse subtree into the local cache for local and LSP analysis. Opt-in on MCP ( ENABLE CLONE=true ); on by default in the CLI. sparsePath Local tools Tool What it does Knob ------ -------------- ------ localSearchCode Local code/text search returning file and line anchors. mode:"structural" runs Octocode AST shape queries ( pattern or rule ). mode localViewStructure Browse a local directory tree: depth, filters, pagination, metadata. detail localFindFiles Find local files and directories by name, path, regex, extension, size, time, permissions, type. localFindDeadCode Find likely-unreferenced exports and dead-code clusters using whole-repository reachability analysis. entrypoints localGetFileContent Read a local file or region: exact slice, match string, line range, or paginated chars. minify Package search Tool What it does Knob ------ -------------- ------ npmSearch npm package lookup and keyword search; returns metadata and the source repository for GitHub handoff. concise LSP Tool What it does ------ -------------- lspGetSemantics Typed semantic navigation: definition , references , callers , callees , callHierarchy , hover , documentSymbols , typeDefinition , implementation , workspaceSymbol , supertypes , subtypes , and diagnostic . From the CLI, invoke it directly: npx octocode tools lspGetSemantics --queries ' >' . Navigation runs through installed language servers (see the LSP tools reference). Full schemas, fields, and examples for every tool live in docs/OCTOCODE TOOLS.md (linked under Documentation). --- MCP The MCP server exposes the Octocode tool catalog directly to your AI assistant over stdio. Manual configuration Add to your MCP client config, using octocode-mcp : Add a GitHub token and options under env - see Authentication and Configuration. --- CLI Same research engine, no MCP client needed. Local paths route to local tools; owner/repo[/path] routes to GitHub. Authenticate once with npx octocode auth login (see Authentication); run npx octocode --help for full usage. Commands Tool commands Command What it does --------- -------------- npx octocode tools > --scheme Show one tool's schema: fields, types, bounds, defaults npx octocode tools > --queries ' >' Run a tool (same tools as MCP), YAML output npx octocode tools > --queries ' >' --json Run a tool, full CallToolResult JSON npx octocode tools List every available tool More commands Cache and clone β€” npx octocode clone , npx octocode cache fetch status clear Skills β€” npx octocode skill list install check info remove for bundled Octocode skills Language servers β€” npx octocode lsp-server list install status uninstall clean Setup and introspection β€” npx octocode install , npx octocode auth , npx octocode status , npx octocode context Full syntax, flags, and exit codes: Octocode CLI guide --- Configuration Everything is optional; Octocode runs on sensible defaults. Settings resolve from three sources, in priority order: MCP / environment variables (highest): per client or per project, set in your MCP config env or your shell. Global config : >/.octocoderc , machine-wide defaults read by both the CLI and the MCP server . Built-in defaults : used when neither is set. Octocode home ( > ) holds the global config, encrypted credentials, sessions, stats, and tmp materialization caches. On every platform it is .octocode inside the OS home directory β€” /.octocode on macOS and Linux, %USERPROFILE%\.octocode on Windows. Override it with OCTOCODE HOME . Set values as MCP env entries (per client; these win over .octocoderc ) or globally in >/.octocoderc (JSON with comments). Tokens never go in .octocoderc β€” use env or npx octocode auth login . Common settings Most-used settings (both CLI and MCP unless noted): Env var .octocoderc key Default What it does --------- ------------------- --------- -------------- OCTOCODE TOKEN / GH TOKEN / GITHUB TOKEN env only unset GitHub token, in priority order. Never in .octocoderc . ENABLE LOCAL local.enabled CLI true ; on MCP set it explicitly Local filesystem and LSP tools on or off. ENABLE CLONE local.enableClone CLI true , MCP false ghCloneRepo + directory fetch on/off. WORKSPACE ROOT local.workspaceRoot cwd Root for resolving relative local paths. ALLOWED PATHS local.allowedPaths [] Extra path allowlist for local access. OCTOCODE OUTPUT FORMAT output.format yaml Response format: yaml or json . OCTOCODE HOME , GitHub Enterprise ( GITHUB API URL ), MCP tool allowlisting ( TOOLS TO RUN / ENABLE TOOLS / DISABLE TOOLS ), and network timeouts/retries: see the Configuration Reference. Example configuration /.octocode/.octocoderc : Per-project overrides and custom LSP servers live in a workspace .octocode/ folder. For the full .octocoderc schema, a ready-to-copy example, clone-cache tuning, GitHub Enterprise setup, and precedence details, see the Configuration Reference. --- Authentication methods GitHub-backed tools require authentication. Any one method is enough. Full details: Authentication Setup. Option 1: Octocode CLI (recommended) Interactive login lets you choose Octocode browser OAuth or gh auth login . Octocode OAuth credentials are stored encrypted on disk. Option 2: GitHub CLI (also supported) Octocode reads the gh token automatically β€” no further config needed. Option 3: Personal access token (also supported) Set O

How do I install Octocode MCP - AI Context Platform?

Run the install command shown above, then paste the config for your client (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) into its MCP settings and restart the client.

Is Octocode MCP - AI Context Platform free to use?

The MCP server itself is free to install. The source is public on https://github.com/bgauryy/octocode-mcp. Any third-party service it calls may require its own API key and account.

Which clients support Octocode MCP - AI Context Platform?

Any MCP-compatible client can use it, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and custom agents.

Add this badge

Publish this server? Link back with a badge on your README or site β€” copy either snippet.

Listed on MCPNav

Markdown

[![Listed on MCPNav](https://mcpnav.net/badge/octocode.svg)](https://mcpnav.net/server/octocode/)

HTML

<a href="https://mcpnav.net/server/octocode/"><img src="https://mcpnav.net/badge/octocode.svg" alt="Listed on MCPNav" height="20"></a>