MCP integrations
Add extra tools to Vicode through MCP servers, each approved before it runs.
MCP (Model Context Protocol) integrations give the AI extra tools beyond the built-in ones for files, commands, notes, and skills.
How Vicode manages MCP
- Integrations are added, launched, and refreshed from inside the app — no hand-edited config files.
- A server does not launch until you approve it, and you can refresh or remove it from the same list.
- Tool calls from an integration show up in the run like any other tool call, with the same approvals.
- Server output is redacted before display, so an integration cannot leak secrets into the conversation.
Official integrations
The in-app catalog curates official integrations. Currently supported:
- shadcn MCP — search, browse, and install components from shadcn-compatible registries.
- Playwright MCP — browser automation for page interaction, testing, and debugging.
Other catalog entries are marked as planned and become installable once they are supported.
Custom servers
You can register your own server as a Vicode-managed MCP connection. Custom servers save as stdio servers and can be scoped to a single project, which fits repo-specific MCP servers and local test harnesses.
Keep it deliberate
An MCP server is a tool with real capability. Add integrations you understand, approve launches deliberately, and review the tool evidence the run leaves behind.