Delv
IDEby Sourcegraph★ 4.3

Sourcegraph Cody (Client)

Cody's IDE plugin acts as an MCP host with deep code-graph context. Works across VS Code, JetBrains, and the Sourcegraph web app.

Homepage MCP docs
A
Safety & Trust

Delv Safety Grade: A

Score 83/100 · assessed 2026-04-19

Maintainer90
Permissions75
Supply chain85
Transparency80
Incidents85

Sourcegraph Cody as an MCP host represents a well-maintained enterprise offering from a legitimate vendor with strong developer tool credentials. The IDE integration provides natural context for MCP servers, though this also means broader permissions than a standalone chat client. Sourcegraph is a known entity in the code intelligence space with active development and enterprise customers. The supply chain is solid through standard IDE plugin distribution channels (VS Code marketplace, JetBrains marketplace). Transparency is good with documentation, though the MCP-specific implementation details are less visible than fully open source alternatives. The main risk vector is that IDE plugins inherently have broad access to your codebase and filesystem, which MCP servers can then leverage. No known security incidents specific to Cody's MCP implementation, though Sourcegraph had a minor credential exposure in 2023 unrelated to Cody.

Green flags

  • Sourcegraph is established enterprise vendor with strong reputation
  • Distributed via official IDE marketplaces (VS Code, JetBrains)
  • Active maintenance and enterprise customer base
  • Code-graph context provides intelligent scoping of MCP queries
  • Settings UI cleaner than manual JSON configuration

Red flags

  • IDE plugins have inherent filesystem:read across entire workspace
  • MCP servers inherit Cody's broad codebase access permissions
  • Closed-source client limits independent security audit
  • 2023 Sourcegraph credential exposure incident (unrelated to Cody)

Permissions requested

Read filesWrite filesOutbound networkRead envRepo readRepo writeExternal LLM call
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

MCP capabilities

  • Tools
  • Resources
  • Prompts
  • Sampling

Platforms

macOSWindowsLinux

Config location

Cody settings under MCP Servers

Review

Cody's MCP support feels like the most natural fit for developers who live in their editor. Unlike Claude Desktop, which bolts MCP onto a chat window, Cody weaves it into the IDE itself. You get autocomplete, inline edits, and chat that can all tap into MCP servers without context switching. The code-graph context is the killer feature: Cody already understands your codebase structure, so when you add an MCP server for, say, database introspection or API docs, it can reason across both. Configuration lives in Cody's settings panel under MCP Servers. It's cleaner than editing JSON files manually, though you still define servers with the same stdio command syntax. The cross-platform story is solid: I've run the same MCP setup on macOS and Linux without translation. JetBrains support means you're not locked into VS Code, though the VS Code experience feels slightly more polished. The MCP implementation is incomplete compared to Claude Desktop. No prompts capability yet, which cuts out pre-packaged workflows some servers offer. No sampling either, so you can't delegate LLM calls back to the client. In practice, tools and resources cover 90% of what I need: fetching data, running commands, exposing context. The missing 10% stings when you hit a server that relies on prompts. Where Cody shines is keeping you in flow. I use it with an MCP server that surfaces internal API specs. Cody's autocomplete suggests function names, then I ask chat to generate the full integration, and it pulls live schema details via MCP without me pasting docs. That loop is faster than bouncing between Claude Desktop and my editor. Rough edges: error messages when an MCP server fails are cryptic. You get a toast notification, but diagnosing stdio issues means tailing logs. The Sourcegraph web app technically supports MCP too, but it's a second-class citizen compared to the IDE plugins. And if you're on a free Cody plan, MCP support might be gated behind enterprise features depending on your org's setup. Check the docs before committing.
Verdict

Best MCP client for developers who want AI assistance without leaving their editor. The code-graph context and inline integration beat standalone chat apps. Skip it if you need full MCP spec support or prefer a dedicated AI chat interface.

Good at

  • Code-graph context merges MCP data with deep codebase understanding
  • Inline autocomplete and edits can use MCP tools, not just chat
  • Cross-platform IDE support (VS Code, JetBrains) with consistent config
  • Settings UI for MCP servers cleaner than manual JSON editing
  • Keeps you in flow: no alt-tabbing to a separate chat app

Watch out

  • No prompts or sampling capabilities yet, unlike Claude Desktop
  • MCP server errors surface as vague toast notifications
  • Sourcegraph web app MCP support lags behind IDE plugins
  • Some MCP features may require enterprise Cody plans
  • Debugging stdio server issues requires log diving