You don\u2019t teach your AI to use EmDash \u2014 EmDash teaches your AI. That flips the usual script. Most CMS platforms bolt AI on as an afterthought: a plugin you install, a prompt you tune, a workflow you hand-craft. EmDash, Cloudflare\u2019s spiritual successor to WordPress, ships with a built-in MCP server and a set of structured skills files. The agent reads them once and knows exactly what it can do. No training. No trial-and-error prompting. The CMS comes with its own instruction manual for machines.<\/p>\n
EmDash\u2019s AI Skills Files are markdown documents that describe every operation the CMS exposes \u2014 create a post, upload media, manage plugins, deploy changes. An MCP-compatible agent (Claude, Cursor, GitHub Copilot) connects to the server, reads the skills files, and can perform those operations using natural language. The agent doesn\u2019t need to guess the endpoint or the parameter format. The skills files provide the schema, the permissions, and the expected output. This means a developer can say \u201cbuild me a new content type for case studies with fields for client name, date, and testimonial\u201d and the agent executes it \u2014 no manual admin clicks.<\/p>\n
Skills files are plain-text documents stored inside the EmDash codebase. Each file describes one capability: how to create a content type, how to import a WordPress export, how to send a test email. They follow the Model Context Protocol<\/a> (MCP) standard that Anthropic created for AI agent<\/a> communication. When an agent connects to EmDash\u2019s MCP server, the server presents these files as available tools. The agent reads the tool definitions, understands the input requirements, and can call them directly.<\/p>\n The files are written in a structured format \u2014 part schema, part example, part human-readable explanation. Here\u2019s a simplified version of what a skills file for \u201ccreate content type\u201d looks like:<\/p>\n “`<\/p>\n Tool: create_content_type<\/p>\n Description: Creates a new content type with custom fields.<\/p>\n Parameters:<\/p>\n Example:<\/p>\n name: “Case Study”<\/p>\n fields:<\/p>\n type: text<\/p>\n type: date<\/p>\n “`<\/p>\n The agent parses this, maps it to the underlying API, and executes. No custom code required.<\/p>\n The MCP route gives you the most leverage. Once the connection is configured, the agent can manage the entire CMS \u2014 content, plugins, themes \u2014 without a human in the loop. The skills files are the instruction set that makes that possible.<\/p>\n You need a running EmDash instance. Use the playground at In the EmDash admin panel, go to Settings \u2192 API Tokens<\/strong>. Create a new token with the scopes your agent will need. For full management, select EmDash exposes an MCP server at “`<\/p>\n {<\/p>\n “mcpServers”: {<\/p>\n “emdash”: {<\/p>\n “url”: “https:\/\/your-site.emdash.app\/mcp”,<\/p>\n “headers”: {<\/p>\n “Authorization”: “Bearer YOUR_API_TOKEN”<\/p>\n }<\/p>\n }<\/p>\n }<\/p>\n }<\/p>\n “`<\/p>\n Ask your agent: \u201cWhat can you do with my EmDash CMS?\u201d The agent will read the skills files and list all available tools. You should see actions like Now give a real instruction:<\/p>\n \u201cCreate a new content type called \u2018Projects\u2019 with fields for Title (text), Description (rich text), and Launch Date (date). Set the slug to \u2018projects\u2019. Add it to the main navigation.\u201d<\/p>\n<\/blockquote>\n blockquoteblockquoteblockquoteblockquote<\/p>\n The agent will call Because the skills files are versioned with the CMS, you can update EmDash and the agent automatically sees new tools. You don\u2019t need to re-train or re-prompt. This is the core advantage: the CMS stays teachable.<\/p>\n Let\u2019s say you have 500 blog posts in WordPress that you want to move to EmDash. Instead of running the built-in import tool manually (which still requires downloading a WXR file and uploading it), you can instruct the agent:<\/p>\n \u201cImport all posts from my WordPress site at example.com. Use the WXR export URL. Map Yoast SEO fields to EmDash\u2019s built-in SEO fields. After import, create a redirect for each old URL to the new path.\u201d<\/p>\n<\/blockquote>\n blockquoteblockquoteblockquoteblockquote<\/p>\n The agent will:<\/p>\n The whole process takes minutes. The agent handles the repetitive mapping and redirection \u2014 tasks that would take a developer hours to script.<\/p>\n\n
\n
\n
\n
\n
\n
Skills Files vs. Traditional CMS Agent Integration<\/h2>\n
\n\n
\n \nInteraction Mode<\/th>\n Setup Effort<\/th>\n Agent Autonomy<\/th>\n Maintainability<\/th>\n Security Model<\/th>\n<\/tr>\n<\/thead>\n \n Admin Panel (UI)<\/td>\n None<\/td>\n Low \u2014 manual clicks only<\/td>\n CMS updates handled by host<\/td>\n Role-based access only<\/td>\n<\/tr>\n \n CLI (Terminal)<\/td>\n Install EmDash CLI, auth<\/td>\n Medium \u2014 scriptable but requires human to run<\/td>\n Must update CLI version manually<\/td>\n Token-based, scoped by role<\/td>\n<\/tr>\n \n MCP with Skills Files<\/td>\n One connection setup (MCP URL + token)<\/td>\n High \u2014 agent can read, write, deploy autonomously<\/td>\n Skills files ship with EmDash updates<\/td>\n Granular permissions per tool via manifest<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Step-by-Step: Connect Your Agent to EmDash Skills Files<\/h2>\n
1. Deploy EmDash (if you haven\u2019t)<\/h3>\n
emdashcms.com<\/code>codecodecodecode (lasts one hour) or deploy to your own Cloudflare account via the GitHub repo. For production, the paid Cloudflare Workers plan ($5\/month) gives you sandboxed plugins and full MCP access.<\/p>\n2. Generate an API Token<\/h3>\n
content:read<\/code>codecodecodecode, content:write<\/code>codecodecodecode, plugins:manage<\/code>codecodecodecode, and settings:read<\/code>codecodecodecode. Copy the token.<\/p>\n3. Configure the MCP Server<\/h3>\n
https:\/\/\/mcp<\/code>codecodecodecode. In your agent\u2019s configuration (Claude Desktop, Cursor settings, or custom app), add a new MCP server:<\/p>\n4. Verify the Connection<\/h3>\n
create_post<\/code>codecodecodecode, update_media<\/code>codecodecodecode, list_plugins<\/code>codecodecodecode, deploy_site<\/code>codecodecodecode. If the list is empty, check the token scopes and the MCP server URL.<\/p>\n5. Run Your First Task<\/h3>\n
\n
create_content_type<\/code>codecodecodecode with the parameters from the skills file, then update the menu via update_menu<\/code>codecodecodecode. No manual admin login required.<\/p>\n6. Iterate with Confidence<\/h3>\n
Real-World Use Case: Bulk Content Migration<\/h2>\n
\n
\n
import_wordpress<\/code>codecodecodecode (a skill file tool) with the file URL.<\/li>\ncreate_redirect<\/code>codecodecodecode.<\/li>\n<\/ol>\nWhy This Changes How You Build Sites<\/h2>\n