MCP servers
WhoseDev inherits Model Context Protocol (MCP) support from its editor foundation. MCP lets the agent call external tools—databases, issue trackers, APIs, and custom services—through standardized servers you install and configure.
Install MCP servers
Section titled “Install MCP servers”Install MCP servers the same way as in VS Code-compatible editors: through the MCP extension ecosystem and registry-connected installs. Check the MCP section in WhoseDev settings or extension marketplace documentation for your build.
Each server exposes tools and resources the agent can use during a session when access is permitted.
Control access
Section titled “Control access”Setting chat.mcp.access controls which installed MCP servers the agent may use:
| Value | Behavior |
|---|---|
none |
No MCP server access |
registry |
Access servers installed from the connected registry |
any |
Access any installed MCP server |
Review this setting before enabling MCP in repositories that handle sensitive data.
Setting chat.mcp.autostart controls whether MCP servers start automatically when you submit chat messages:
| Value | Behavior |
|---|---|
never |
Never auto-start servers |
onlyNew |
Start servers that have never been run |
newAndOutdated |
Start new and outdated servers that are not yet running |
Additional MCP settings
Section titled “Additional MCP settings”| Setting | Purpose |
|---|---|
chat.mcp.gallery.enabled |
Enable the MCP marketplace for discovering servers |
chat.mcp.collisionBehavior |
When two servers share a name: disable lower-priority duplicates or suffix with numeric suffixes |
chat.mcp.serverSampling |
Control which models MCP servers may call for background sampling |
chat.mcp.ui.enabled |
Allow MCP servers to provide custom UI for tool invocations |
Run MCP: List Servers from the Command Palette to inspect installed servers and sampling permissions.
Use MCP with the agent
Section titled “Use MCP with the agent”When MCP access is allowed and servers are running, MCP tools appear alongside built-in WhoseDev tools in agent sessions. Approve high-risk operations the same way you would terminal or file tools.
MCP complements—not replaces—workspace rules and skills. Use MCP for live external systems; use rules and skills for repository-specific conventions.