A brief becomes a real page.Custom Post Type UI MCP integration
Add the content types a site needs, without writing code.
EMCP saves post types and taxonomies through Custom Post Type UI's own functions, so they appear in CPT UI and register on the next page load. Create a post type with its labels, visibility and editor features, add a taxonomy for it, then refine the labels. Slugs never change once created.
Free integrationCustom Post Type UI 1.19.3
One post type, one taxonomy
| Step | What EMCP does |
|---|---|
| 01 · Check | Slug recipe is free |
| 02 · Post type | Recipes, four editor features |
| 03 · Taxonomy | Cuisine, hierarchical, on Recipes |
| 04 · Register | Rewrite rules refreshed |
A practical place to start
From an idea to a registered content type.
- 01
Check what exists
list-registered-post-types shows every public post type and whether CPT UI owns it, so a new slug never collides with another plugin's.
- 02
Create the type and taxonomy
create-post-type takes a slug, labels, a description, visibility and editor features. create-taxonomy attaches a taxonomy to one or more public post types.
- 03
Refine the labels
update-post-type and update-taxonomy change labels and descriptions with the version from the last read. The slug stays as it is.
Built for Custom Post Type UI
CPT UI’s own save, nothing executable
EMCP fills in CPT UI’s own save functions, the ones behind its admin forms, so the stored definition is exactly what CPT UI would write. It never writes code, custom capability types or callbacks, and refuses definitions that rely on them or on settings another extension stored, because CPT UI’s save would drop those.
Slugs that stay put
A slug is fixed at creation, so posts, terms and URLs keep working. Reserved WordPress names, slugs another plugin already registered and prefixes such as wp_, acf_ and elementor are refused before anything is saved.
Undo that respects your content
Label and description edits restore the earlier text. Undoing a creation removes the definition only while nothing uses it: no posts in any status, including the trash, no terms and no other definition referring to it. Every change is in History in EMCP Tools or EMCP Lite.
Use the Custom Post Type UI tool reference for operation names and arguments, and the Pods integration when the new type also needs fields.
Get connected
Put Custom Post Type UI in your AI’s toolkit.
- 1
Install Custom Post Type UI
Install EMCP Tools 3.21.1 or later, or EMCP Lite 1.0.5 from WordPress.org, with Custom Post Type UI 1.19.3. Other versions are refused until they are qualified.
- 2
Enable the write tool
cptui-read is on; cptui-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > Custom Post Type UI and reconnect your AI client.
- 3
Describe the content
Tell your AI what the content is and which fields of the editor it needs: title, editor, featured image, excerpt and so on.
Then connect Claude Code, Claude Desktop, or Cursor to use the Custom Post Type UI tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Custom Post Type UI, supported operations, and the workflow on your site.
Can I undo a new post type?
Yes, while it is empty. Undo removes the definition only when no posts in any status, terms or other definitions depend on it, and force does not change that.
Will the block editor work with the new type?
Set show_in_rest to true and include editor in supports. The block editor needs the REST API.
Why was an update refused?
Either the definitions changed since your read, or the definition carries settings CPT UI's own save would discard, such as custom capabilities or keys added by an extension.
Does it add fields?
No. Use Pods, ACF or Meta Box for custom fields on the new type.
Your tools. Your WordPress site.