Connect VS Code
VS Code can work on your SitePack site through the connector, from GitHub Copilot's agent mode. It uses the Model Context Protocol (MCP), so once it is connected you can ask Copilot to read or change your site's content, on the one site you approve.
VS Code with GitHub Copilot and agent mode. MCP tools are used by the agent, not by plain chat.
Connect with browser sign-in
Add the connector to a mcp.json file. Put it in .vscode/mcp.json for a single workspace, or add it to your user settings for every workspace. Or run the command MCP: Add Server from the Command Palette and follow the prompts.
{
"servers": {
"sitepack": {
"type": "http",
"url": "https://admin.sitepack.eu/api/mcp"
}
}
}
The first time VS Code starts the server it asks you to allow it and then opens the SitePack sign-in and the permission screen in your browser. Choose your site and press Approve. VS Code remembers the sign-in afterwards.
Open the Copilot Chat view, switch it to Agent mode, and the SitePack tools appear in the tools list.
In agent mode, ask: "With the SitePack tools, list the pages that have no meta description." Copilot will call the connector and show the result.
What you can do
The same tools as every SitePack connection: pages, menus, media, products, categories, tags and translations, on the one site the connection is bound to. See Connect Claude for the full list, and the overview for exactly what you approve.
Frequently asked questions
The tools don't appear in chat
MCP tools are only used in agent mode, not in the default chat or edit modes. Switch Copilot Chat to Agent mode and check the tools list. See Troubleshooting for more.
Does VS Code get access to my whole account?
No. Like every SitePack connection, it is bound to one site and to the permissions you approve, and it never requests anything that spends money.
How do I disconnect?
Remove the sitepack entry from your mcp.json, or stop the server from the MCP servers view.