Expansions MCP Server

Connect your tools to Content Hub.

The Expansions MCP Server is a remote service you add to your AI coding tool — Claude Code, Claude Desktop, Cursor or VS Code. Add one endpoint and your API key, and your assistant can plan, build, test and deploy Sitecore Content Hub features, with CH connectivity, per-user memory and the full developer toolset built in.

New to MCP? The Model Context Protocol is a standard way to give an AI assistant new abilities. You add the Expansions endpoint to your tool once — from then on, your assistant has every Content Hub tool below. Nothing to install, no local process to run.

Pick your client Request an API key

How the connection works

One HTTP endpoint

The server speaks stateless streamable-HTTP. There's nothing to install and no local process — your client connects directly to https://mcp.expansions.dev.

One API key

Authenticate with a single header, Authorization: Bearer <your-api-key>. The server validates it and tracks credits per call. Keep the key secret.

Pick your toolset

Connect to the full toolset or a slimmer subset to save tokens. /mcp/core/ is the recommended daily driver.

Endpoints

The same server exposes several endpoints — choose the one that matches what your client needs (you can connect to more than one at once):

https://mcp.expansions.dev/mcp/core/         — recommended daily driver (~15 tools)
https://mcp.expansions.dev/mcp/              — everything (all tools)
https://mcp.expansions.dev/mcp/sitecore-write/  — CH writes, schema, GraphQL
https://mcp.expansions.dev/mcp/scripting/    — CH script push / get / scan
https://mcp.expansions.dev/mcp/git/          — GitHub OAuth + workspace git ops
https://mcp.expansions.dev/mcp/scaffold/     — one-time workspace bootstrap
https://mcp.expansions.dev/mcp/admin/        — user & API-key administration

Connect your client

Every example uses the recommended /mcp/core/ endpoint and a Bearer token. Swap in your own key, and switch the URL to another endpoint above whenever you need a different toolset.

Claude Code

claude mcp add --transport http expansions https://mcp.expansions.dev/mcp/core/ \
  --header "Authorization: Bearer <your-api-key>"

Or add it to ~/.claude.json:

{
  "mcpServers": {
    "expansions": {
      "type": "http",
      "url": "https://mcp.expansions.dev/mcp/core/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop:

{
  "mcpServers": {
    "expansions": {
      "type": "http",
      "url": "https://mcp.expansions.dev/mcp/core/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in the project root:

{
  "mcpServers": {
    "expansions": {
      "url": "https://mcp.expansions.dev/mcp/core/",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

VS Code — GitHub Copilot (agent mode)

Create .vscode/mcp.json in your workspace. The key is read from a secure prompt instead of being stored in the file:

{
  "servers": {
    "expansions": {
      "type": "http",
      "url": "https://mcp.expansions.dev/mcp/core/",
      "headers": { "Authorization": "Bearer ${input:expansions-key}" }
    }
  },
  "inputs": [
    { "id": "expansions-key", "type": "promptString", "password": true,
      "description": "Expansions API key" }
  ]
}

Other MCP clients

Windsurf, Continue, Cline and any other MCP client work the same way — the only differences are the config file and the key used for the server URL:

Windsurf — ~/.codeium/windsurf/mcp_config.json, use "serverUrl" for the URL.
Continue — ~/.continue/config.yaml, type: streamable-http with the header under requestOptions.
Cline (VS Code) — cline_mcp_settings.json, "type": "streamableHttp".
Microsoft Copilot Studio / M365 — add an MCP server with URL https://mcp.expansions.dev/mcp/core/ and the same Bearer auth.

Any programmatic client

Anything that speaks streamable-HTTP can connect:

Endpoint: POST https://mcp.expansions.dev/mcp/core/
Transport: streamable-HTTP (stateless — no session reuse required)
Auth: Authorization: Bearer <your-api-key> on every request
Discovery: the standard tools/list MCP method

Need an API key?

Expansions is in private rollout with selected partners. Request a key and we'll get you connected.

[email protected]