Add an MCP server to VS Code
Install from a listing into VS Code with the MCP extension. Or add the PlugMCP directory MCP so the agent finds the server for you.
VS Code talks to MCP servers through its MCP support. A listing on PlugMCP still points at the publisher's URL or command. You paste that into VS Code, or you add the PlugMCP directory MCP first and ask the agent which server to install.
From a listing
- Open the server page in the directory.
- Copy the VS Code snippet from the install block. It is the publisher's remote URL or local command.
- In VS Code, open the MCP configuration (Command Palette → MCP: Open User Configuration, or the workspace
mcp.jsonyour team uses). - Paste the snippet, save, and reload MCP. Ask the agent to list tools and confirm the server appears.
Remote servers use a URL. Local servers use a command such as npx or uvx. The listing page shows which shape you have. For the difference, see /blog/remote-url-vs-local-command.
Let the agent find the server
If you are not sure which server to add, install the PlugMCP directory MCP from /directory-mcp. That is the MCP for MCPs: the agent searches the catalog and returns the install config for VS Code. Setup steps for each client are on /docs/connect.
When the server is your own API or app and you want keys and call logs, host it on /host. VS Code then uses the same https://mcp.plugmcp.ai/s/{slug} URL as Cursor and Claude.