You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Split line 9 in README.md (28 words → 18 + 11 words)
- Changed "easy" to "quickly" in best-practice/README.md line 59
- Updated "umbraco" to "Umbraco" for consistency
- Changed "excellent" to "good" for more measured tone
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: 16/umbraco-cms/reference/developer-mcp/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ description: Get started with the CMS developer MCP.
6
6
7
7
The Developer [MCP Server](./concepts/model-context-protocol.md#mcp-servers) makes it straightforward for developers to connect AI tools with Umbraco. It allows you to harness large language models (LLMs) to perform almost any task that can be achieved within the Umbraco backoffice. This includes generating and editing content, managing media, automating workflows, and assisting with complex development tasks.
8
8
9
-
This MCP Server acts as a secure gateway between your Umbraco installation and MCP-compatible AI environments such as Claude (Desktop or Code), Cursor, or GitHub Copilot.
9
+
This MCP Server acts as a secure gateway between your Umbraco installation and MCP-compatible AI environments. These include Claude (Desktop or Code), Cursor, or GitHub Copilot and many more.
10
10
11
11
Through this bridge, your AI assistant can interact directly with Umbraco's Management API. This enables a more natural, conversational way to develop and maintain your sites.
12
12
@@ -115,7 +115,7 @@ Although the details vary slightly, the general pattern is the same across all h
115
115
116
116
```
117
117
118
-
Add your Umbraco MCP configuration values (Client ID, Client Secret, URL of umbraco) in the appropriate section of your host setup. Then restart the MCP Server or, in some cases, restart the host application itself.
118
+
Add your Umbraco MCP configuration values (Client ID, Client Secret, URL of Umbraco) in the appropriate section of your host setup. Then restart the MCP Server or, in some cases, restart the host application itself.
119
119
120
120
Once restarted, you’ll have access to the full suite of tools available through the Umbraco CMS Developer MCP Server.
121
121
@@ -129,7 +129,7 @@ You can check your current Node.js version by running node -v in your terminal.
129
129
{% hint style="danger" %}
130
130
**Critical: Do not connect the Developer MCP Server to a production Umbraco environment.**
131
131
132
-
The Developer MCP Server provides powerful, direct access to your Umbraco Management API. While this makes it an excellent tool for development and testing, mistakes can have serious consequences. Misconfigurations or misunderstood commands can cause immediate and potentially destructive damage.
132
+
The Developer MCP Server provides powerful, direct access to your Umbraco Management API. While this makes it a good tool for development and testing, mistakes can have serious consequences. Misconfigurations or misunderstood commands can cause immediate and potentially destructive damage.
Copy file name to clipboardExpand all lines: 16/umbraco-cms/reference/developer-mcp/best-practice/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Large prompts and bloated toolsets not only lead to slower and less accurate res
27
27
- Monetary cost (especially on usage-based APIs)
28
28
- Compute usage, which has a direct carbon footprint
29
29
30
-
Being intentional with your prompts and tool selection isn’t just a technical best practice — it’s a sustainable one.
30
+
Being intentional with your prompts and tool selection isn’t only a technical best practice — it’s a sustainable one.
31
31
32
32
{% hint style="info" %}
33
33
Optimising your context makes your work faster, cheaper, and greener.
@@ -42,7 +42,7 @@ Open a new session in your LLM client (e.g., Claude Desktop, Cursor or others).
42
42
Identify which MCP tools you'll need for the specific task. Avoid loading unnecessary functionality.
43
43
44
44
3. Update the environment variables
45
-
Use .env or launch-time environment variables to switch tool configs easily.
45
+
Use .env or launch-time environment variables to switch tool configs.
46
46
47
47
4. Run your prompt or workflow
48
48
Ask the model to perform the task. Keep it focused on the tools you've enabled.
@@ -56,7 +56,7 @@ For fast, flexible configuration changes, manage tool settings using environment
56
56
57
57
## Context Condensing
58
58
59
-
Large Language Models have a limited context window, and every active tool, message, and instruction contributes to that total. If you're working on a complex or long-running task, it's easy to hit the limit — especially when multiple tools are enabled.
59
+
Large Language Models have a limited context window, and every active tool, message, and instruction contributes to that total. If you're working on a complex or long-running task, you can quickly hit the limit — especially when multiple tools are enabled.
60
60
61
61
To help manage this, you can condense context to keep the model focused and free up space.
0 commit comments