1. SitecoreAI documentation for developers

Sitecore Developer MCP server

The Sitecore Developer MCP server connects AI coding agents to SitecoreAI development tools through the Model Context Protocol (MCP). It provides tools for creating and updating components and content types, configuring component availability for sites, and creating content items. Developers and AI agents can use these tools from MCP clients to carry out component development and content modeling workflows.

The Developer MCP server uses Streamable HTTP and MCP OAuth. The production server URL is https://edge-platform.sitecorecloud.io/mcp/developer, and the server name is sc-developer.

Important

The Sitecore Developer MCP server is currently in beta and we’re actively seeking feedback from developers and early adopters. Your input will help shape future enhancements as we work toward general availability.

Features

The Developer MCP server supports the following capabilities:

  • Component management - list components and component summaries, retrieve component details, create and update components, and list component categories.
  • Content modeling - list, retrieve, create, and update content types, and retrieve available validation rules.
  • Site discovery and content creation - list sites and create content items under an existing parent using a specified content type.

Setup

Follow the procedure for your preferred client to configure a connection to the production Developer MCP server.

Cursor IDE

To set up the connection:

  1. Add the following configuration to ~/.cursor/mcp.json or .cursor/mcp.json:

    {
  "mcpServers": {
    "sc-developer": {
      "url": "https://edge-platform.sitecorecloud.io/mcp/developer"
    }
  }
}

  2. Sign in using the browser prompt that the client opens.

For more information, see the Cursor MCP documentation.

Visual Studio Code

To set up the connection:

  1. Add the following configuration to .vscode/mcp.json:

    {
  "servers": {
    "sc-developer": {
      "type": "http",
      "url": "https://edge-platform.sitecorecloud.io/mcp/developer"
    }
  }
}

  2. Sign in using the browser prompt that the client opens.

For more information, see Add an MCP server and the MCP configuration reference.

Claude Code

To set up the connection:

  1. Run the following command:

    claude mcp add --transport http sc-developer https://edge-platform.sitecorecloud.io/mcp/developer

  2. Sign in using the browser prompt that the client opens.

For more information, see the Claude Code MCP documentation.

Codex

To set up the connection:

  1. Add the following configuration to ~/.codex/config.toml:

    [mcp_servers.sc-developer]
url = "https://edge-platform.sitecorecloud.io/mcp/developer"

  2. Run the following command:

    codex mcp login sc-developer

  3. Sign in using the browser prompt that the client opens.

For more information, see the Codex MCP documentation.

OpenCode

To set up the connection:

  1. Add the following configuration to opencode.json:

    {
  "mcp": {
    "sc-developer": {
      "type": "remote",
      "url": "https://edge-platform.sitecorecloud.io/mcp/developer"
    }
  }
}

  2. Run the following command:

    opencode mcp auth sc-developer

  3. Sign in using the browser prompt that the client opens.

For more information, see the OpenCode MCP servers documentation.

Authentication

The Developer MCP server uses MCP OAuth with no headers. Sign in using the browser prompt that your client opens.

Example

User prompt: Create a Testimonial component for Skatepark, with quote, author name, role, and a portrait. Keep it consistent with Skatepark's templates.

Note

The steps an agent takes when it uses the MCP server, and the results it produces, can vary between runs.They depend on the AI model, your prompt, and the existing content and customizations on your site. Review all changes before you publish.

What happens:

  • The agent identifies the Skatepark site.
  • The agent retrieves existing components, component categories, and relevant content types to identify Skatepark’s naming conventions and field definitions
  • The agent inspects suitable content types using and uses these definitions to propose fields for the quote, author name, role, and portrait. If the existing definitions do not establish a suitable pattern, the agent asks you to clarify
  • The server creates a Testimonial content type following the identified conventions. If a suitable content type already exists, the agent can reuse it.
  • The server registers the Testimonial component. The initial request includes the content type ID, an appropriate component category, and Skatepark’s site ID.
  • The agent retrieves the component and content type to verify the model association and field definitions.
  • The server returns the component ID and content type ID.
If you have suggestions for improving this article, let us know!