Umbraco MCP. Control content, media, and drafts autonomously.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Umbraco MCP Server gives your AI agent full control over Umbraco CMS content and media. You can list public pages, create drafts in the backoffice, update existing documents, or pull specific assets—all using natural conversation.
It handles everything from structured data retrieval to binary file management without you touching a GUI.
What your AI agents can do
Create cms document
Creates a brand new document within the Umbraco CMS using provided JSON data and adhering to defined schemas.
Delete cms document
Permanently removes an existing document from the Umbraco CMS. This action cannot be undone.
Get delivery content by id
Retrieves a specific published content item using its unique GUID or numeric ID via the Delivery API.
Retrieves a specific published piece of content using only its full web path, like /products/new-feature.
Grabs a complete list of every Document Type (schema) defined in your Umbraco environment.
Pushes new document drafts into the CMS by providing structured data as a JSON object.
Modifies specific fields of an existing Umbraco document using its ID and updated JSON data.
Permanently removes a draft or published document from the Umbraco system.
Filters and lists content items using specialized query syntax, such as finding all entries with contentType:blogPost.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Umbraco MCP Server: 10 Tools for Content Management
Use these tools to manage the entire lifecycle of Umbraco content, from listing media assets to updating live drafts via API calls.
019d7618create cms document
Creates a brand new document within the Umbraco CMS using provided JSON data and adhering to defined schemas.
019d7618delete cms document
Permanently removes an existing document from the Umbraco CMS. This action cannot be undone.
019d7618get delivery content by id
Retrieves a specific published content item using its unique GUID or numeric ID via the Delivery API.
019d7618get delivery content by path
Fetches a specific piece of published content by knowing its exact URL path (e.g., '/contact').
019d7618get management document
Retrieves drafts or non-published documents directly from the Umbraco backoffice using the Management API.
019d7618list delivery content
Lists content available through the Delivery API, supporting pagination when dealing with large datasets.
019d7618list document types
Provides a full list of all document types (schemas) defined and used within your Umbraco site.
019d7618list media assets
Lists every media asset, such as images or files, stored in the Umbraco Media library.
019d7618query delivery content
Filters and searches content items using advanced query syntax specific to the Umbraco Delivery API.
019d7618update cms document
Updates fields of an existing document in Umbraco by providing its ID and a JSON object containing the changes.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Umbraco, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Listen up. This Umbraco MCP Server gives your AI agent full control over the entire CMS content and media stack. You don't gotta touch the GUI or wrestle with dashboards—your agent handles everything using natural conversation.
Here’s how you use it:
Content Retrieval & Publishing:
- You can pull up specific, published content pieces by knowing their exact URL path; for instance, if someone hits
/products/new-feature, your agent pulls that whole article. If you know the unique GUID or numeric ID of a live piece, it grabs that too using the Delivery API. - Want to see everything public? Your agent lists all available content through the Delivery API and handles pagination so you don't miss anything in large sites.
- You can filter down massive datasets by type—say, pulling only entries where
contentType:blogPostexists. This tool uses advanced query syntax specific to Umbraco’s Delivery API, letting your agent search like a pro.
Backoffice Drafting & Management:
- Need to work on something that isn't ready for the public? Your agent fetches drafts or non-published documents directly from the Umbraco backoffice using the Management API. This means you can review content before it ever hits the live site.
- If you gotta make a new document draft, your agent builds it for you. It creates brand new documents in the CMS by accepting structured data via JSON and making sure that payload adheres to the required schema definition.
- When an existing document needs a tweak, your agent updates those fields for you. You just give it the ID and a JSON object containing only the changes you want, and it pushes them live.
- Sometimes, content gotta go. Your agent permanently deletes any draft or published document in Umbraco; remember, this action is irreversible.
Schema and Asset Control:
- You can check out every single Document Type (schema) used across the site by calling a list of all available schemas tool. This gives you a complete map of your content structure.
- For media management, your agent lists every asset—images, PDFs, whatever—stored in the Umbraco Media library. It's like getting a full inventory count of everything attached to the CMS.
Basically, it lets your AI client perform all the standard CRUD operations right inside the engine room. You tell your agent what you need done—like 'find all product pages that reference the Q3 report' or 'create a draft for the updated privacy policy'—and it handles the back-end REST calls through both the public Delivery API and the private Management/Backoffice APIs.
No more switching between an IDE, a terminal, and the CMS dashboard. Your agent manages it all.
How Umbraco MCP Works
- 1 First, you subscribe to the Umbraco MCP server on Vinkius and inject your required Umbraco Base URL and Management Auth Token.
- 2 Second, you ask your AI client (e.g., Cursor) to perform an action—like 'list all media assets' or 'create a draft for the About page'.
- 3 The agent translates that request into specific tool calls (
list_media_assetsorcreate_cms_document), executes them against Umbraco, and returns the structured data.
The bottom line is: your AI client talks to Umbraco directly using defined API functions, skipping any manual UI steps entirely.
Who Is Umbraco MCP For?
CMS Platform Engineers who hate switching contexts between code and content dashboards. Digital Editors who need to review or update raw content drafts without navigating deep into the GUI. Frontend Architects who need reliable, pure JSON payloads for visual testing.
Automates routine headless content extractions and requests specific schema structures from the agent instead of writing boilerplate code.
Asks the agent to bulk-view lists of raw content items, bypassing complex table drill-downs in the Umbraco admin panel.
Quickly confirms internal content API stability by extracting pure JSON payloads that map exactly to visual components.
What Changes When You Connect
- Full Lifecycle Control: Don't just read data. Use
create_cms_documentto push new drafts orupdate_cms_documentto modify existing fields without logging into the CMS GUI. - Targeted Retrieval: Forget general searches. Fetch content using its exact path (
get_delivery_content_by_path) or query only by schema type (query_delivery_content). - Schema Awareness: Use
list_document_typesto know exactly what data structures exist before you try to populate a payload, saving hours of guesswork. - Media Asset Inventory: Need to track every image? Run
list_media_assetsto get an absolute list of all binary files stored in the Umbraco library. - Draft Management: Access non-published content using
get_management_document, allowing your agent to work with drafts before they ever hit production.
Real-World Use Cases
Need to audit all product schema types.
A Platform Engineer needs to know if a new product line requires a 'ProductVariant' type. Instead of clicking through the CMS administration, they ask their agent to run list_document_types. The agent replies with an immediate list, letting them verify the exact schema name needed for coding.
Correcting a typo on a live page.
A Digital Editor spots a title error on /about-us. They ask their agent to use get_delivery_content_by_path first, confirming the current content and ID. Then, they instruct the agent to use update_cms_document, providing only the JSON payload with the corrected text.
Building a data migration script.
A Frontend Architect needs all old blog post contents for a new site build. They ask their agent to run query_delivery_content filtered by contentType:blogPost, getting structured JSON payloads ready to map directly into the headless application.
Clean up outdated drafts.
A CMS Admin wants to delete a batch of obsolete documentation. They ask their agent to list all documents via list_delivery_content (using pagination), identify the specific GUIDs, and then run delete_cms_document on each one.
The Tradeoffs
Trying to read content without a path.
Asking the agent simply to 'get me the product page.' This is vague and doesn't specify where in Umbraco the item lives, leading to an error or a massive list dump.
→
Always use get_delivery_content_by_path and provide the full URL (e.g., /products/widget-x). If you only have the ID, run get_delivery_content_by_id instead.
Updating content without knowing the schema.
The user tries to update a field called 'productDescriptionLong' but Umbraco uses 'descriptionText'. The API rejects the payload because the key doesn't match any defined Document Type.
→
First, run list_document_types to see available schemas. Then, use the correct keys when calling update_cms_document.
Assuming all content is published.
A developer tries to read a draft document using only the Delivery API endpoint. The request fails because drafts are managed by the separate backoffice system.
→
Use get_management_document when you specifically need to interact with unpublished or draft versions of content.
When It Fits, When It Doesn't
You use this server if your workflow requires autonomous, stateful interactions inside Umbraco. Think: 'I need the AI agent to perform a multi-step task that involves reading data and then writing changes.' Use it when you're building an automated pipeline or prototype content flow.
Don't use this if you simply need to read static, public data for display (a simple HTTP GET call is fine). Also, don't rely on it if your process requires transactions across multiple CMS platforms—it only talks to Umbraco. If you are just listing available content types, list_document_types handles that; don't try to use it for reading the actual data.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Umbraco. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Dealing with Content APIs shouldn't mean switching between 5 different tabs.
Today, updating content is a pain. You find the item in the CMS GUI. You copy its GUID. You switch to your local IDE to grab the schema structure. Then you write boilerplate code just to make a simple PATCH request back into Umbraco. It's constant context switching and manual data plumbing.
With this MCP server, you eliminate that entire headache. Your agent handles it all in one chat window. You simply tell your agent: 'Update the title of the product at `/widgets/new` to X.' The agent calls `update_cms_document`, runs the API call, and confirms the change—all without you leaving your primary development tool.
Umbraco MCP Server: Get data, create content, manage media.
Manual processes used to require separate calls for everything: one API call just to list the types (`list_document_types`), another to fetch a specific item (`get_delivery_content_by_path`), and yet a third step just to get the media assets (`list_media_assets`). This was slow, brittle, and required complex orchestrating code.
Now, your agent coordinates all that. You can ask it: 'List all blog posts AND grab their featured image.' The agent runs `query_delivery_content` and then calls `get_delivery_content_by_id` while pulling the media details via `list_media_assets`. It delivers one complete, usable JSON object.
Common Questions About Umbraco MCP
How do I get a draft document using get_management_document? +
You use this tool to retrieve drafts or non-published content that isn't visible via the standard Delivery API. You must specify the document ID and provide your management credentials.
Can I bulk create multiple documents with create_cms_document? +
Yes, you supply a list of JSON objects to the tool call. The agent processes them one by one, creating multiple new drafts or structured records in Umbraco.
What's the difference between get_delivery_content_by_id and query_delivery_content? +
get_delivery_content_by_id retrieves one item when you know its GUID. query_delivery_content is for searching—it filters a large set of content items based on criteria like content type or author.
How do I update fields using update_cms_document? +
You pass the document's ID and then provide a JSON payload. The keys in your JSON must match the actual field names defined by the schema for that document type.
When using list_delivery_content, how do I fetch content beyond the first page? +
You must manage pagination using the take and skip parameters. Send a request with a smaller batch size (e.g., take=50) and increment the skip value on successive calls to iterate through all available items.
Before I use create_cms_document, how do I find out what content schemas exist? +
You need to run list_document_types. This tool returns a complete catalog of every document type (schema) configured in Umbraco. Use this list to ensure your JSON payload matches the required structure.
What is the primary use case for list_media_assets? +
This tool pulls metadata on all binary assets—images and files—stored in the media library. It doesn't touch content; it gives you a comprehensive inventory of your media resources.
If I run delete_cms_document, is there any way to recover that data? +
No. This action permanently removes the document from the Umbraco CMS context and cannot be undone by the AI agent or through subsequent API calls. Be certain of your target ID before executing it.
Can it easily retrieve the content of a page assuming I only know its URL path? +
Absolutely. Instruct the agent to 'get_delivery_content_by_path' and supply something like '/home/about'. It traverses the Delivery API native routing map and returns perfectly all inner block grids and content variables attached.
How do I ensure the JSON payloads for `create_cms_document` are exactly what Umbraco expects? +
Use the agent to first run 'list_document_types'. It pulls down the global schema blueprints. The LLM can explicitly read the allowed field types (like rich text or media pickers) and logically construct the insertion matching it exactly.
Does it pull media details dynamically? +
Yes. Pinging 'list_media_assets' grants full insight over all stored visuals inside your Umbraco media containers, returning URL addresses alongside fundamental dimension formats so the agent can reference them anywhere.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ImageKit (Media Optimization & DAM)
Manage and optimize media via ImageKit — list files, purge CDN cache, and audit image metadata.
HashiCorp Nomad
Manage workloads and orchestration via Nomad — track jobs, nodes, and deployments directly from your AI agent.
Bitbucket
Manage your Git repositories via Bitbucket — list pull requests, commits, and pipelines directly from any AI agent.
You might also like
Cin7 Core
Equip your AI agent to manage inventory, sales orders, and purchase orders via the Cin7 Core (formerly DEAR Systems) API.
Dexatel
Equip your AI agent to send SMS messages, track communications, and manage contacts via the Dexatel API.
Elai AI Video
Equip your AI agent to generate AI videos, manage avatars, and track rendering status via the Elai.io API.