For Sitecore Content Hub teams

Ship Content Hub features in days, not months.

Expansions is an 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.

Request access How it works

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.

How Expansions works

Two products, one workflow. The Expansions MCP Server builds and ships your features, while the free Content Hub Navigator — a Chrome extension and an in-app widget — keeps you and your team moving fast around the tenant. Here's a real task, end to end.

  1. 1

    Connect your AI tool with the Expansions MCP Server

    Add the Expansions MCP Server to Claude Code, Claude Desktop, Cursor or VS Code. 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." Expansions 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 Expansions 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, so the whole team finds things in one click.

Connect the tools you already use

The Expansions MCP Server is a remote server 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 gains the full Content Hub developer toolset. No local install, no extra infrastructure.

One endpoint

Connect directly to mcp.expansions.dev over stateless streamable-HTTP. Choose the full toolset or a slim /mcp/core/ subset to save tokens.

One API key

Authenticate with a single Authorization: Bearer header. Credits are tracked per call, so you only pay for what your team actually runs.

Your client of choice

Works with Claude Code, Claude Desktop, Cursor, VS Code (Copilot), Windsurf, Continue, Cline, Microsoft Copilot — or any MCP client.

See connection guides All supported clients

Content Hub Navigator Free

A free companion to the Expansions MCP Server — free to use, for your whole team. Jump to any page in your Content Hub tenant in one click: users, schema, scripts, triggers, settings and more, always scoped to the environment you're already in. Two ways to run it, same Navigator:

Chrome extension

Navigate from your browser toolbar

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.

Get the Chrome extension

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

External Page Component

Embed it inside Content Hub itself

A single JavaScript file you embed in Content Hub. The same Navigator ships as a floating widget you drop into your master layout via an External Page Component — no per-user install, no asset upload to maintain. It's served live from our CDN, so it always stays current.

Embed instructions

Embed the navigator widget

Add the hosted script below to your Content Hub master layout as an External component. Because it's loaded from our CDN at runtime, you get updates automatically — there's nothing to re-upload.

https://cdn.expansions.dev/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.expansions.dev/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.

Who Expansions 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.

Request access

Expansions is in private rollout with selected partners. To request access or a walkthrough, get in touch.

[email protected]