Connect your tools to Content Hub.

The Xpansions MCP Server is a remote service you add to your AI coding tool — Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue, Zed, JetBrains or OpenAI Codex. Add one endpoint, sign in — 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. No keys to copy.

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

Connect your tool

How the connection works

One endpoint

The server speaks stateless streamable-HTTP — nothing to install, no local process. Every tool lives at a single URL: https://xpansions.net/mcp/

Sign in once

Your tool shows a sign-in prompt the first time it hits the server. Approve in your browser — done. Your session renews itself; you never see or copy a key.

Your tool of choice

Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue, Zed, JetBrains AI Assistant, OpenAI Codex — or any OAuth-capable MCP client. Same endpoint, same setup.

Connect in two steps

Pick your tool below. Add the endpoint, sign in when prompted — and you're connected. No account needed beforehand; signing in for the first time creates your free account automatically.

Claude Code

Step 1 — in your terminal (outside any claude session), register the server:

claude mcp add --transport http xpansions https://xpansions.net/mcp/

Step 2 — start Claude Code (claude), then type /mcp in the chat. Select xpansions from the list and choose Authenticate. Your browser opens — sign in with your email, click Approve, return to your terminal. Done.

If /mcp shows "No MCP servers configured", Step 1 was run from a different directory. Re-run it from the directory where you use Claude Code, or add --scope user to register it once for all projects.

Claude Desktop

Step 1 — open Customize → Connectors, click +, choose Add custom connector, and fill in:

Name: Xpansions
Remote MCP server URL: https://xpansions.net/mcp/
Click Add

Step 2 — the OAuth screen opens in your browser. Sign in, click Approve, return to Claude Desktop. Done.

Status indicators in Customize → Connectors: no icon = connected | ✕ = disconnected (click to reconnect) | ⚠ = error (check auth or server availability).

Cursor

Step 1 — open Settings → Tools & MCP, click + Add new MCP server, set transport to Streamable HTTP, name it xpansions, and paste the URL. Or add directly to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "xpansions": {
      "url": "https://xpansions.net/mcp/"
    }
  }
}

Step 2 — on the first tool call, Cursor opens your browser for sign-in. Complete the OAuth flow and you're connected.

VS Code GitHub Copilot agent mode

Step 1 — press Cmd / Ctrl+Shift+P, run MCP: Add Server, choose HTTP, enter https://xpansions.net/mcp/ as the URL, and name it xpansions. Or create .vscode/mcp.json in your workspace:

{
  "servers": {
    "xpansions": {
      "type": "http",
      "url": "https://xpansions.net/mcp/"
    }
  }
}

Step 2 — switch to Agent mode (Cmd / Ctrl+I → select Agent). On first use, VS Code prompts for sign-in — approve in your browser.

MCP tools are only active in Agent mode. They are not visible in Ask or Edit modes.

Windsurf

Step 1 — add to ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json):

{
  "mcpServers": {
    "xpansions": {
      "serverUrl": "https://xpansions.net/mcp/"
    }
  }
}

Windsurf uses serverUrl — not url.

Step 2 — restart Windsurf. Xpansions tools appear in the Cascade panel. Sign in when prompted to complete the OAuth flow.

Cline VS Code extension

Step 1 — open the Cline sidebar in VS Code, click MCP Servers, select the Remote Servers tab, and click Add Remote Server:

Server Name: xpansions
Server URL: https://xpansions.net/mcp/
Click Add Server

Step 2 — Cline opens your browser for sign-in. Complete the OAuth flow and return.

Continue

Step 1 — add to ~/.continue/config.yaml:

mcpServers:
  - name: xpansions
    transport:
      type: streamable-http
      url: https://xpansions.net/mcp/

Step 2 — reload the window (Cmd / Ctrl+Shift+P → Developer: Reload Window). Xpansions tools appear in the Continue chat panel.

Zed

Step 1 — open Zed → Settings (Cmd / Ctrl+,) and add to settings.json:

{
  "context_servers": {
    "xpansions": {
      "url": "https://xpansions.net/mcp/"
    }
  }
}

Step 2 — Zed opens your browser to authenticate on first use. Your session is stored in the system keychain — you only sign in once.

JetBrains IDEs AI Assistant

Works in IntelliJ IDEA, PyCharm, WebStorm, GoLand and all other JetBrains IDEs with the AI Assistant plugin.

Step 1 — open Settings → Tools → AI Assistant → Model Context Protocol (MCP), click +:

Name: xpansions
URL: https://xpansions.net/mcp/
Click OK and apply settings

Step 2 — AI Assistant opens a browser for OAuth sign-in. Approve and return to your IDE.

OpenAI Codex

Step 1 — add to ~/.codex/config.toml (global) or .codex/config.toml (project-scoped):

[mcp_servers.xpansions]
url = "https://xpansions.net/mcp/"

Step 2 — run codex. On the first Xpansions tool call, Codex opens a browser for OAuth sign-in. Approve and return — session is stored securely for future runs.

Any other MCP client

Any client that speaks streamable-HTTP works with the same endpoint. Add https://xpansions.net/mcp/ as an HTTP server with no auth header — the server automatically triggers the OAuth sign-in flow on the first request.

Other clients known to work: Roo Code, Amazon Q Developer, Sourcegraph Cody, Microsoft Copilot Studio, and any client built on MCP SDK 1.0+.

You can see and disconnect connected apps any time from your account portal.

Then: connect to your Content Hub tenant

Once your AI tool is talking to Xpansions, ask it to connect to Content Hub — e.g. "connect me to Content Hub at https://yourtenant.sitecorecontenthub.cloud". Your assistant walks you through the rest; here's what to expect at each step.

1. Tenant check

Your assistant asks for your Content Hub URL and checks it's reachable. No Content Hub credentials needed for this step.

2. Choose how to sign in

Recommended — an OAuth client on your tenant: you sign in on Content Hub's own page, so your Content Hub username and password never reach Xpansions at all.

No-setup fallback — username + password: a hosted Xpansions page relays your sign-in to Content Hub instead. Simpler, but your password does pass through Xpansions once, in flight, to complete the exchange — nothing is stored, but the OAuth client path avoids this entirely.

3. Set up the OAuth client recommended path

In Content Hub, create an M.OAuthClient entity (ask your Content Hub admin if you don't have access) with a client ID, a client secret, and this exact redirect URL:

https://xpansions.net/ch/oauth/callback

This has to match character-for-character — scheme, host, path, no trailing slash — or Content Hub rejects the sign-in with invalid_client: The specified 'redirect_uri' is invalid. Content Hub entity edits often need to be published before they take effect, not just saved as a draft — and double-check you're editing the entity whose client ID matches the one you're using, if your tenant has more than one.

4. Save your credentials locally

Give your assistant the client ID and secret once. If it has file access (Claude Code, Cursor, VS Code), it stores them for you at ~/.xpansions/ch.env — in your home directory, outside any git repo, reusable across every project you work in:

CH_SERVER_URL=https://yourtenant.sitecorecontenthub.cloud
CH_CLIENT_ID=your-client-id
CH_CLIENT_SECRET=your-client-secret

You only do this once — from then on your assistant reads this file instead of asking again. Keep it out of any repo you commit.

5. Sign in and grant access

Your assistant opens a link to Content Hub's own sign-in page. Enter your Content Hub username and password there, then approve the consent screen Content Hub shows you. Your assistant detects the moment you're connected automatically — no need to say "done."

6. You're connected

Ask for anything — "list my entity definitions," "get a random asset," "create a draft M.Asset." Access renews itself automatically in the background using the same stored credentials; you won't need to sign in again unless you disconnect.

Prefer the simple path? Skip step 3 — just give your assistant the tenant URL and it uses the no-setup username+password page instead.

Need an account?

Signing in for the first time creates your free account automatically — no card required, nothing to set up beforehand.

Create free account Sign in