A brief becomes a real page.Pods MCP integration
Structured content in Pods, filled in by conversation.
EMCP works through the Pods API on public post-type Pods that store fields as post meta. Create a Pod with its fields, add draft records with their values, and update a record later with a version check. Pods applies its own field permissions, and every save is read back.
Free integrationPods 3.3.9.2
One Pod, three records
| Step | What EMCP does |
|---|---|
| 01 · Pod | Properties, 4 fields, read back |
| 02 · Records | 3 drafts with values |
| 03 · Update | Bedrooms changed, version checked |
| 04 · History | Value edit undoable |
A practical place to start
From a list of items to Pods records.
- 01
Create the Pod
create-pod takes a name, a label and up to 20 fields of type text, paragraph, number or boolean. EMCP reads the saved Pod back field by field.
- 02
Add records
create-record adds a draft with a title and field values, authored by the connected user, so nothing is published before you look.
- 03
Keep them up to date
update-record changes field values with the record's version. A record changed since your read is refused, and the edit can be undone.
Built for Pods
The Pods API, with checks around it
EMCP saves through Pods itself: save_pod for a new Pod, the Pods object for records. Pods applies its own permissions to every field, and EMCP reads the result back. A save that Pods or another plugin’s hook changed on the way is reported as a partial write with the IDs it created, never as success.
Fields that stay simple
Each value must match its field: a whole number for a number field, true or false for a boolean, plain text for text and paragraph fields. A value that does not fit is refused before anything is saved, and a field used twice in one call is refused too.
Versions and undo
Every Pod and record answers a version. Pass it to label and value edits; a record changed in between is a conflict. Value and label edits can be undone from History, unless the Pod’s fields changed since, which force does not override. Every change is in History in EMCP Tools or EMCP Lite.
Use the Pods tool reference for operation names and arguments. To register a post type without fields, use Custom Post Type UI.
Get connected
Put Pods in your AI’s toolkit.
- 1
Install Pods
Install EMCP Tools 3.21.1 or later, or EMCP Lite 1.0.5 from WordPress.org, with Pods 3.3.9.2. Other versions are refused until they are qualified.
- 2
Enable the write tool
pods-read is on; pods-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > Pods and reconnect your AI client.
- 3
Share the data
Give your AI the list of items and the fields each one has.
Then connect Claude Code, Claude Desktop, or Cursor to use the Pods tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Pods, supported operations, and the workflow on your site.
Can it create relationship fields?
No. It creates and writes text, paragraph, number and boolean fields only. Other field types are listed as not writable.
Why is creation not undoable?
Removing a Pod or record automatically could take later content with it. Creation is recorded in History with the new IDs, and you remove them in Pods if needed.
Can it publish records?
New records are always drafts. Publish them in the editor or with the WordPress content tools.
Does it accept HTML in fields?
No. Text and paragraph values must be plain text, so a value that contains HTML tags is refused.
Your tools. Your WordPress site.