Cloudflare’s EmDash CMS launched as version 0.1.0. The plugin marketplace sits empty. That’s not a bug—it’s an opening.
Because EmDash ships with a built-in MCP server and agent skills files, you can generate plugins using natural language. No PHP required. No WordPress hooks to memorize. The sandboxed runtime handles security for you.
WordPress took 20 years to accumulate 60,000 plugins. EmDash has zero today. That's not a weakness. It's a canvas.
Here are seven plugins you can build today with Claude, Cursor, or any MCP-compatible coding agent. Each one solves a real WordPress pain point that EmDash doesn’t yet cover natively.
1. Content Blocker for Drafts That Shouldn’t Go Live
The problem: You schedule a post. You forget to remove a placeholder paragraph. It publishes at 3 AM.
The plugin: On the post:publishcodecodecodecode hook, this plugin checks the post body for a list of blocked phrases (like “TODO: add real content here” or “lorem ipsum”). If found, it reverts the post to draft and sends you an email notification.
What to tell your AI agent: “Create an EmDash sandbox plugin that registers a hook on post:publishcodecodecodecode. When triggered, scan the post content for these three blocked phrases. If any match, set the post status back to ‘draft’ and use the email:sendcodecodecodecode capability to notify the site admin.”
The agent will generate a definePlugincodecodecodecode function with capabilities read:contentcodecodecodecode, write:contentcodecodecodecode, and email:sendcodecodecodecode. It’s roughly 40 lines of TypeScript.
2. AI-Generated Meta Descriptions
The problem: Yoast SEO doesn’t exist on EmDash yet. You’re writing meta descriptions by hand.
The plugin: On post:savecodecodecodecode, this plugin reads the post body, calls an AI API (via a declared http:postcodecodecodecode capability), and writes the returned summary into the SEO meta description field.
The catch: Sandboxed plugins can’t make arbitrary network calls by default. You must declare http:postcodecodecodecode with a specific domain in the manifest. The plugin only talks to one API endpoint.
What to tell your AI agent: “Build a sandbox plugin that listens to post:savecodecodecodecode. Extract the first 1000 characters of content. Send a POST request to https://api.openai.com/v1/completions with a prompt asking for a 155-character meta description. Write the response to the seo.metaDescriptioncodecodecodecode field. Capabilities: read:contentcodecodecodecode, write:contentcodecodecodecode, http:postcodecodecodecode.”
3. Scheduled Email Newsletter Digests
The problem: EmDash has no built-in email campaign system. WordPress sites rely on Mailchimp plugins that don’t exist here.
The plugin: A sandbox plugin that runs on a cron-like schedule (every 7 days). It queries posts published in the last week, formats them into an HTML email, and sends it to a list of subscribers stored in a custom content type.
The technical detail: Dynamic workers cold-start in milliseconds. A scheduled plugin that runs weekly consumes near-zero billable compute. Compare that to a WordPress cron job hitting a PHP server.
What to tell your AI agent: “Create a plugin with a scheduled hook. Query all posts with status ‘published’ from the last 7 days. Generate an HTML email template with titles and excerpts. Send it via the email:sendcodecodecodecode capability to all entries in the ‘subscribers’ collection. Capabilities: read:contentcodecodecodecode, email:sendcodecodecodecode, read:subscriberscodecodecodecode.”
4. Form Submission Spam Filter With Turnstile
The problem: EmDash ships with a form plugin, but no built-in spam protection. Your portfolio site’s contact form fills with garbage.
The plugin: A sandbox plugin that intercepts form submissions before they’re saved. It validates a Cloudflare Turnstile token attached to the submission. If the token is missing or invalid, the submission is discarded with no database write.
What makes this possible: Turnstile is free. The plugin only needs one http:postcodecodecodecode capability to verify the token against Cloudflare’s API. No CAPTCHA UI changes needed on the frontend.
What to tell your AI agent: “Build a plugin that hooks into form:submitcodecodecodecode. Extract the turnstileTokencodecodecodecode field from the submission payload. Send a POST request to https://challenges.cloudflare.com/turnstile/v0/siteverify with the token and secret key. If the response indicates failure, delete the submission. Capabilities: read:formcodecodecodecode, delete:formcodecodecodecode, http:postcodecodecodecode.”
5. Auto-Tagging Media Uploads
The problem: Every uploaded image sits in the media library with no alt text, no tags, no description. Accessibility and SEO suffer.
The plugin: On media:uploadcodecodecodecode, the plugin reads the image file (via read:mediacodecodecodecode), extracts metadata, and writes a human-readable description to the media entry using a simple lookup table or a local classification model.
The information gain: This plugin doesn’t need an external AI API. You can embed a small lookup table that maps common image dimensions, file types, and naming patterns to descriptions. A file named “team-photo-2025.jpg” gets tagged “Team photo from 2025.” No network calls, no latency, zero ongoing cost.
What to tell your AI agent: “Create a plugin on media:uploadcodecodecodecode that reads the file name and file type from the media metadata. Apply a simple pattern: if the filename contains ‘team’ or ‘group’, set description to ‘Team photo’. If it contains ‘logo’, set description to ‘Company logo’. Write the result to the media entry. Capabilities: read:mediacodecodecodecode, write:mediacodecodecodecode.”
6. Custom Analytics Dashboard
The problem: EmDash has no analytics. You’re guessing which posts perform.
The plugin: A sandbox plugin that logs a page:viewcodecodecodecode event to a D1 database table every time a post is rendered. It exposes a simple admin panel widget showing top posts by views in the last 30 days.
Why this matters for billing: Each page view triggers a single D1 write. At 10 million requests per month on the $5 plan, a personal blog won’t crack the billing ceiling. But this is where the serverless cost concern becomes real for high-traffic sites—every view is a metered action.
What to tell your AI agent: “Build a plugin that registers a page:rendercodecodecodecode hook. Increment a counter in the D1 database for the current post ID. Add an admin widget that queries the top 10 posts by view count and displays them as a list. Capabilities: read:contentcodecodecodecode, write:d1codecodecodecode.”
7. Simple Paywall With 402 Payments
The problem: You want to charge for premium content. WordPress needs a subscription plugin. EmDash supports the 402 payment protocol natively.
The plugin: A sandbox plugin that checks whether a post belongs to the “premium” category. If yes, it intercepts the render and returns a 402 Payment Required response with a Lightning Invoice or a standard payment request. Paid requests get a signed token that bypasses the block for 24 hours.
The nuance: This isn’t a full membership system. It’s a single HTTP status code and a token check. But it’s native to the platform—no Stripe plugin, no WooCommerce. The 402 protocol is built into the EmDash core.
What to tell your AI agent: “Create a plugin on post:rendercodecodecodecode that checks the post’s categories. If the category slug is ‘premium’, check for a valid x-pay-tokencodecodecodecode header. If missing, return a 402 status with a payment URL. Capabilities: read:contentcodecodecodecode, read:categoriescodecodecodecode.”
The Pattern That Makes This Work
Every plugin above follows the same structure: a hook, a capability manifest, and a single-purpose function. The AI agent writes the code. You review the capabilities list. The dynamic worker enforces the boundary.
The mistake beginners make is asking for too much at once. “Build me a full e-commerce system.” That’s 50 plugins. Start with one hook, one capability, one output. Test it in the playground. Then expand.
WordPress took 20 years to accumulate 60,000 plugins. EmDash has zero today. That’s not a weakness. It’s a canvas.
- What is the EmDash plugin marketplace like?The EmDash plugin marketplace is currently empty, but that's an opportunity because plugins can be generated using natural language.
- How do you build an AI-generated meta description plugin?Create a sandbox plugin that listens to post:save, extracts content, sends a POST request to an AI API, and writes the response to the SEO meta description field.
- What is the 402 payment protocol in EmDash?The 402 payment protocol is a native EmDash feature that allows plugins to return a 402 Payment Required response with a Lightning Invoice for premium content.
