For Sitecore Content Hub teams


Ship Sitecore Content Hub features in days, not months.

Xpansions is the MCP server and AI development backbone for Sitecore Content Hub. Your team plans, builds, tests and deploys features in a fraction of the time — without rewriting how you work.

Works with the AI coding tools your team already uses

  • Claude Code
  • Claude Desktop
  • Cursor
  • VS Code
  • GitHub Copilot
  • Microsoft Copilot
  • OpenAI Codex
  • Windsurf
  • Continue
  • Cline
  • …or any MCP client

Who Xpansions is for

Sitecore partners

Delivery teams under fixed-scope, fixed-deadline pressure who need to multiply the throughput of every Content Hub engineer on the bench.

In-house Content Hub teams

Enterprise teams running Content Hub as part of a wider martech stack who want to move faster on internal feature requests without growing headcount.

The Content Hub delivery bottleneck

Boilerplate eats the sprint

Half of every Content Hub project is plumbing — schema wiring, action scripts, portal pages, integration glue. The interesting work waits behind it.

Senior expertise doesn't scale

Few engineers know Content Hub deeply. Those who do become bottlenecks, reviewing the same patterns over and over for juniors who can't ship without them.

Iteration is slow and risky

Cycle times stretch into weeks because every change has to be planned, written, manually tested and reviewed across a fragmented stack.

One workflow, from prompt to production

Two products work together:

Xpansions MCP Server — the engine. Plans, builds, tests and ships your Content Hub features.

Content Hub Navigator — the companion. Gets anyone to the right page in one click. Two ways to deploy: as a Chrome extension for individuals, or an External Page Component (JS file embedded in your master layout) for the whole team. Here's a real task, end to end.

  1. 1

    Connect your AI tool with the Xpansions MCP Server

    Add the Xpansions MCP Server to Claude Code, Claude Desktop, Cursor, VS Code, GitHub Copilot, Microsoft Copilot or OpenAI Codex. Your assistant instantly understands your Content Hub schema, conventions and existing code — no re-platforming, no migration. See the connection guides →

  2. 2

    Describe the feature in plain language

    Ask for something real — for example, "Add a Campaign entity with a linked-assets relation and a branded preview component." Xpansions plans it, then generates the entity definitions, action scripts, React components and C# integration code to match how your team already builds.

  3. 3

    It tests, fixes and deploys to your sandbox

    Generated code is tested automatically. When something breaks, the Xpansions MCP Server fixes it and retries until it's green, then deploys to your sandbox. Your team reviews and ships.

  4. 4

    Navigate and verify with the Content Hub Navigator

    Open the Content Hub Navigator Chrome extension to jump straight to the new Campaign entity, its schema or the scripts you just generated — no hunting through menus. Then roll the same Navigator out to your editors as an in-app widget via the External Page Component, so the whole team finds things in one click.

Xpansions MCP Server Free

An AI Content Hub developer, on demand

A remote MCP server you add to your AI coding tool — Claude Code, Claude Desktop, Cursor, VS Code, GitHub Copilot, Microsoft Copilot, OpenAI Codex or any MCP client. Add one endpoint and your assistant gains the full Content Hub developer toolset. No local install, no extra infrastructure.

One endpoint

Add xpansions.net/mcp in your AI tool and connect over stateless streamable-HTTP — one URL, the full Content Hub developer toolset, ready to use.

One click to connect

Your tool shows a Connect link the first time. Click it, sign in with your email, approve — done. No key to copy for interactive use; API keys available for CI and headless environments.

Your AI tool of choice

Works with Claude Code, Claude Desktop, Cursor, VS Code, GitHub Copilot, Microsoft Copilot, OpenAI Codex, Windsurf, Continue, Cline — or any MCP client.

Content Hub Navigator · Chrome extension Free

Any Content Hub page, one click away

A Chrome extension you install in your browser. Pin the Content Hub Navigator and click it on any Content Hub tab — it auto-detects the active tenant and opens a categorized menu of admin destinations. No bookmarks, no remembered paths, nothing sent to third-party servers.

One click to any page

Jump to users, schema, scripts, triggers, settings and more — always scoped to the tenant you're currently browsing.

Auto-detects the tenant

Works across all your environments. Switch tabs, the navigator switches with you — no config per tenant.

Nothing leaves your browser

The extension reads the current tab URL to detect the tenant. No data is sent to external servers.

✓ Live on the Chrome Web Store — free to install.

The Navigator is powered by Xpansions. When you're ready to do more than navigate, the Xpansions MCP Server plans, builds, tests and ships your Content Hub features end to end. Try the MCP Server →

Content Hub Navigator · External Page Component Free

The same Navigator, for your whole team

Some organizations don't allow browser extensions — so the same Navigator also ships as an in-app widget. It's a single JavaScript file you embed in Content Hub through a master layout External Page Component: the same one-click Navigator, available to your whole team inside Content Hub with nothing to install in anyone's browser and no IT approval to chase. Served live from our CDN, so it always stays current.

No extension, no IT approval

Ideal where browser extensions are blocked. One embed in the master layout gives every user the Navigator — editors, admins and developers alike — with nothing to install per person.

Always up to date

The widget is loaded from our CDN at runtime. Updates ship automatically — there's nothing to re-upload or redeploy.

Five-minute setup

Open your master layout, add an External component, point it at the JS bundle URL, save. Done.

Embed instructions

Add this URL as a JS Bundle External Page Component in your Content Hub master layout:

https://cdn.xpansions.net/ContentHubNavigator.js
  1. Open your master layout

    In Content Hub, go to Manage → Master layouts and select the layout your pages use — most use Basic.

  2. Add an External component

    Choose Add component and select External.

  3. Point it at the JS bundle

    Select JS Bundle, then set Path to JS bundle to https://cdn.xpansions.net/ContentHubNavigator.js.

  4. Save

    Save the master layout and reload Content Hub. The navigator appears as a floating widget, scoped to the current tenant — no further configuration required.

Rolling the free Navigator out to your team? That's Xpansions too — the same platform behind the MCP Server that turns plain-language requests into shipped Content Hub features. Try the MCP Server →

Frequently asked questions

What is the Sitecore Content Hub MCP server?

It's a remote MCP (Model Context Protocol) server that gives your AI coding tool a full Sitecore Content Hub developer toolset. Add one endpoint — xpansions.net/mcp — and your assistant can plan, build, test and deploy Content Hub features end to end.

Which AI tools and MCP clients does it work with?

Claude Code, Claude Desktop, Cursor, VS Code, GitHub Copilot, Microsoft Copilot, OpenAI Codex, Windsurf, Continue, Cline — or any client that speaks MCP over streamable-HTTP.

Is Xpansions free?

Yes — create an account in seconds, no card required. The Content Hub Navigator (Chrome extension and in-app widget) is free too.

How much time does Xpansions save?

Most of a Content Hub build is repeatable boilerplate — schema wiring, action scripts, portal pages and integration glue. By generating, testing and fixing that work, Xpansions can free up roughly 70% of the time normally spent on plumbing. These are illustrative estimates, not measured client averages; real savings depend on feature scope and tenant complexity.

What is the Content Hub Navigator?

A free companion that gets anyone to the right Content Hub page in one click. It comes in two forms: a Chrome extension for individuals or an External Page Component for the whole team.

Do I need to install a browser extension?

No. If your organization blocks browser extensions, use the in-app widget instead — a single JavaScript file embedded in your Content Hub master layout, with nothing for individual users to install.

How do I connect to the MCP server?

Add https://xpansions.net/mcp/ in your AI tool, click Connect, sign in with your email and approve. API keys are available for CI and headless use. See the connection guides.

Get started for free

Create an account in seconds — no card required. Free to use.