xSpeed Cache is officially live! Get 50% OFF during Launch Week — Lifetime starts at just $79Lifetime from $79 — 50% OFF, Launch Week! See Plans →

See Plans →
Features
xSpeed Hub Pricing Docs Blog Scan
Appearance
Get Plugin

Connect GitHub Copilot in VS Code to xSpeed Hub MCP

AI & MCP 3 min read Updated Oct 2026

Add xSpeed Hub to VS Code with one mcp.json entry, sign in once, and ask GitHub Copilot to manage your WordPress sites from the Chat view.

You add one MCP server, xspeedhub, to your VS Code user configuration. GitHub Copilot’s agent in the Chat view can then use the Hub’s tools.

Before you start

You need a free xSpeed Hub account with at least one site connected. Connect your sites to xSpeed Hub first if you have not.

Steps

  1. Add xSpeed Hub to your user mcp.json

    Open the Command Palette and run MCP: Open User Configuration, then add this entry. Servers in your user profile are available in every workspace. MCP: Add Server walks you through the same thing, and the project-level .mcp.json file works too if you want the entry shared with your team; that file uses a top-level mcpServers object instead of servers.

    mcp.json (MCP: Open User Configuration)
    {
      "servers": {
        "xspeedhub": {
          "type": "http",
          "url": "https://app.xspeedcache.com/xspeed/mcp"
        }
      }
    }
  2. Start the server and sign in

    Run MCP: List Servers, pick xspeedhub and choose Start. VS Code asks whether you trust the server, then opens a browser page where you sign in to xSpeed Hub and approve access. There is no token to paste, and VS Code keeps the credentials it receives. Open the Chat view and use the Configure Tools button to see the xSpeed tools.

    Text
    MCP: List Servers

Sign-in

OAuth sign-in or connection token. VS Code starts the OAuth flow on first connection, beginning with dynamic client registration, and opens a browser page where you approve access in xSpeed Hub. If you prefer a header, add the connection token from the Hub's Connect AI page under headers, using a VS Code input variable so it is not saved in the file.

Alternative

Or use a connection token

Copy the connection token from Connect AI in the Hub (only the workspace owner sees it). The input variable makes VS Code ask for the token once and store it, instead of leaving it in the file.

mcp.json (MCP: Open User Configuration)
{
  "inputs": [
    {
      "type": "promptString",
      "id": "xspeed-token",
      "description": "xSpeed Hub connection token",
      "password": true
    }
  ],
  "servers": {
    "xspeedhub": {
      "type": "http",
      "url": "https://app.xspeedcache.com/xspeed/mcp",
      "headers": { "Authorization": "Bearer ${input:xspeed-token}" }
    }
  }
}

Check it worked

Ask GitHub Copilot in VS Code this. It only reads, so nothing changes on your sites.

Prompt
Using xSpeed Hub, which of my sites has the lowest cache hit ratio? Only read; do not change anything.

A first prompt

Prompt
Use xSpeed Hub to list my sites and show page cache status for each one.

If something does not work

  • A chat request can enable at most 128 tools. xSpeed Hub adds 29, so if you also run other MCP servers, deselect some in the tools picker when VS Code reports too many.
  • Workspace MCP files such as .mcp.json are committed with the project and inherit Workspace Trust. Put the xSpeed entry in your user configuration unless you want teammates to get it too, and never put a connection token in a shared file.
  • The VS Code documentation lists .vscode/mcp.json as a deprecated destination for new servers. Use the user configuration or a portable .mcp.json.
  • Organizations can manage MCP access through GitHub policies, so a managed account may not be able to add a server at all.