Extensions and the connector marketplace
Distinguish editor extensions, agent skills, and MCP connector setup.
Choose the right kind of extension
Section titled “Choose the right kind of extension”| You need | Use |
|---|---|
| Reusable instructions for an agent task | Skills |
| Editor language support or editor UI features | The editor’s Extensions view |
| Tools from another service | MCP and the connector catalog |
| A separate coding agent in native chat | Agent Client Protocol |
These are separate systems. Installing a skill does not install a service, and installing an editor extension does not automatically expose tools to the native agent.
MCP connector catalog
Section titled “MCP connector catalog”V3Code’s connector marketplace is a catalog of MCP servers, not the editor extension marketplace. Open Settings → MCP Servers to review available connections and their setup requirements.
Some connectors need a sign-in flow, others need credentials or a local executable. Follow the card’s setup action, inspect its reported status, and verify that tools are available before asking the agent to use them. Availability in the catalog does not mean the service is authenticated or working.
Editor extensions
Section titled “Editor extensions”Use the editor’s Extensions view for editor add-ons. Check publisher, compatibility, permissions, and installation errors. An extension may depend on APIs or services that are not available in this build.
Plugin compatibility is not automatic
Section titled “Plugin compatibility is not automatic”V3Code does not promise that another agent’s plugin manifest, marketplace source, hook format, or slash commands can be copied into the native editor unchanged. Use the documented skill format, MCP configuration, or the external agent’s own setup.
Only install code and connectors you trust. Tool access can expose project files and, for browser-enabled agents, signed-in pages. See Other agents and Privacy.