umbraco

This MCP server gives your agent access to Umbraco's Management API, enabling automated back-office tasks such as retrieving culture information, querying and managing data types, dictionaries, and documents, among other capabilities. The server authenticates with an Umbraco API user, and permissions control what actions the agent can perform. Tools are exposed through the MCP interface and can be enabled or disabled via environment configuration. Typical usage involves starting the MCP server with your Umbraco credentials and then issuing prompts that leverage the available tools—for example querying for the GUID of a page document type, listing data types, or fetching dictionary entries. You can tailor the available tools by excluding specific management tools if needed, using the EXCLUDE_MANAGEMENT_TOOLS option.

Prerequisites:

• Node.js and npm installed on your machine
• Access to an Umbraco instance with an API user (client ID and secret) and the base URL of your Umbraco Management API

Installation steps:

1. Install Node.js (which includes npm) from https://nodejs.org
2. Ensure you have access to the Umbraco API user credentials (Client ID, Client Secret) and the base URL (e.g., https://your-umbraco-domain/ Umbraco API base)
3. Run the MCP server using the recommended npx command:

npx @umbraco-mcp/umbraco-mcp-cms@alpha

4. Provide required environment variables when starting the server, for example:

UMBRACO_CLIENT_ID=<API user name>
UMBRACO_CLIENT_SECRET=<API client secret>
UMBRACO_BASE_URL=https://<domain>

5. If you need to configure the MCP within another tooling environment (Claude, VS Code, Cursor, etc.), use the following config example which maps to the same npm package:

{
  "mcpServers": {
    "umbraco-mcp": {
      "command": "npx",
      "args": ["@umbraco-mcp/umbraco-mcp-cms@alpha"],
      "env": {
        "UMBRACO_CLIENT_ID": "<API user name>",
        "UMBRACO_CLIENT_SECRET": "<API client secret>",
        "UMBRACO_BASE_URL": "https://<domain>"
      }
    }
  }
}

Optional: If you need to exclude certain tools, you can add EXCLUDE_MANAGEMENT_TOOLS in the env block as shown in the repository examples.

Tips and notes:

• Ensure the Umbraco API user has appropriate permissions for the actions you intend to perform.
• If you encounter TLS/connectivity issues with a self-signed certificate, you may need to set UMBRACO_BASE_URL to the correct host and consider configuring TLS settings in your environment. Some setups reference NODE_TLS_REJECT_UNAUTHORIZED=0; add this only if you understand the security implications.
• Logs can help diagnose connectivity issues; look for mcp-server-umbraco-mcp.log in the relevant log directory when problems arise.
• Tools exposed include retrieval and management of Culture, Data Type, Dictionary, and Document related actions. You can further tailor the available tools by excluding ones you don’t want the agent to use via environment configuration.
• The MCP server configuration shown here is compatible with editors like Claude Code, Claude Desktop, VS Code MCP integration, and Cursor; adapt the env vars accordingly for each tool integration.