> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-in-ai/mcp/mcp-servers/cms-developer-mcp/skills-and-cli.md).

# Skills & CLI

Use the Developer MCP Server's Claude Code plugin skills, or the server itself as a CLI tool, for a quick connection to Umbraco without additional setup.

The Developer MCP Server ships a Claude Code plugin with skills for CLI operation and MCP client setup. The server can also be used as a CLI tool directly. This wraps the same MCP server and exposes the same tools, but runs them from the command line.

The MCP connection is more context-efficient because the host manages tool selection and conversation state. The skills and CLI below are a simpler alternative. Use them to get started quickly, debug your configuration, or have Claude Code walk you through setup.

## Installing the Plugin

```bash
/plugin marketplace add umbraco/Umbraco-CMS-MCP-Dev
/plugin install umb-cms-mcp@umb-cms-mcp-plugins
```

## `umb-cms-dev-cli`

Guide for running and debugging the Developer MCP Server via the CLI. It covers listing tools, calling tools directly, tool filtering, dry-run and readonly modes, and debugging your resolved configuration.

Use it with a query to interact with Umbraco directly from Claude Code:

```
/umb-cms-dev-cli tell me what properties the home document type has
/umb-cms-dev-cli list all published content under the homepage
/umb-cms-dev-cli show me the media library structure
```

For the full reference of CLI flags, runtime modes, introspection commands, and input sanitization, see the [CLI Reference](https://docs.umbraco.com/umbraco-in-ai/mcp/custom-mcp-server/sdk/cli.md).

## `umb-cms-mcp-setup`

Guide for installing and configuring the Developer MCP Server as a live MCP connection in an AI client, rather than running it standalone. Supported clients include Claude Desktop, Claude Code, Cursor, and GitHub Copilot.

Use it when you want Claude Code to walk you through connecting the server for the first time, or to troubleshoot an existing connection. It points to the same official setup guides as this documentation site:

* [Getting Started](https://docs.umbraco.com/umbraco-in-ai/mcp/mcp-servers/cms-developer-mcp.md)
* [Local MCP Setup](https://docs.umbraco.com/umbraco-in-ai/mcp/connect-to-an-mcp-server/local-mcp-setup.md)
* [Configuration Options](https://docs.umbraco.com/umbraco-in-ai/mcp/mcp-servers/cms-developer-mcp/configuration.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-in-ai/mcp/mcp-servers/cms-developer-mcp/skills-and-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
