In earlier posts I demonstrated two code‑based approaches to move the same FAQ item between the two platforms:

• An Authoring API sample that pushed data into Sitecore.
• A Management API sample that sent updates into Umbraco.

Both approaches relied on a small .NET minimal API code snippet. This follow‑up keeps the goal and removes the code entirely: two MCP servers and a single chat prompt handle the full round‑trip.

Minimal MCP configuration

{
    "servers": {        
        "Sitecore": {
            "type": "stdio",
            "command": "npx",
            "args": ["@antonytm/mcp-sitecore-server@latest"],
            "env": {
                "TRANSPORT": "stdio",
                "GRAPHQL_ENDPOINT": "https://xmcloudcm.localhost/sitecore/api/graph/",
                "GRAPHQL_SCHEMAS": "edge,master,core",
                "GRAPHQL_API_KEY": "{6D3F291E-66A5-4703-887A-D549AF83D859}",
                "GRAPHQL_HEADERS": "",
                "ITEM_SERVICE_DOMAIN": "sitecore",
                "ITEM_SERVICE_USERNAME": "admin",
                "ITEM_SERVICE_PASSWORD": "b",
                "ITEM_SERVICE_SERVER_URL": "https://xmcloudcm.localhost/",
                "POWERSHELL_DOMAIN": "sitecore",
                "POWERSHELL_USERNAME": "admin",
                "POWERSHELL_PASSWORD": "b",
                "POWERSHELL_SERVER_URL": "https://xmcloudcm.localhost/",
            }
        },
        "Umbraco": {
            "command": "npx",
            "args": ["@umbraco-mcp/umbraco-mcp-cms@alpha"],
            "env": {
                "UMBRACO_CLIENT_ID": "<API user name>",
                "UMBRACO_CLIENT_SECRET": "<API client secert>",
                "UMBRACO_BASE_URL": "https://<domain>",
                "EXCLUDE_MANAGEMENT_TOOLS": "<toolname>,<toolname>"
            }
        },
    }
}

Follow the instructions in these repositories to get a setup similar to this example:

• Sitecore MCP server: https://github.com/Antonytm/mcp-sitecore-server
• Umbraco MCP server: https://github.com/Matthew-Wise/umbraco-mcp

That’s it. Once configured, the two MCP servers can work together automatically.

Umbraco to Sitecore

I used the following chat command:

Find the FAQ item in Umbraco and Sitecore. Copy the content from Umbraco to Sitecore add to the title field and text field it has been edited by MCP.

The prompt at the top of the chat window kicks off a chain of MCP tool calls. First, search runs in both Umbraco and Sitecore so the servers can locate the matching items on either side. After that, MCP gets the text from the Umbraco item and edits the Sitecore item with the copied content plus the edited by MCP suffix.

In the screenshot you can see green check marks beside the calls that have completed, while a spinner shows a call that is still retrying, usually because the first payload didn’t match the schema on the target CMS.

Opening the Sitecore editor shows the new title and text, both tagged edited by MCP.

Sitecore to Umbraco

I used the following chat command:

Find the FAQ item in Umbraco and Sitecore. Copy the content from Sitecore to Umbraco add to the title property and text property it has been edited by MCP again.

The prompt above triggers the same sequence in reverse. A search runs in both systems, MCP gets the content from Sitecore, and then edits the Umbraco item with the updated text. No extra mapping is needed because the servers already understand the field layout on each side.

The Umbraco back‑office now shows the updated answer tagged edited by MCP again.

Conclusion

One MCP server already handles a wide range of operations inside a single CMS. Add a second server and you can enable two‑way content sync when required. With only a small JSON file and a chat prompt, you get a no‑code workflow that can keep Sitecore and Umbraco content aligned, and there are many more possibilities once you start combining MCP servers and tools.