Custom fields integration

MCP for Pods

Pods decides per pod whether values live in post meta or in the pod's own table. WP MCP handles both on the plugin-data pair: pods-list-fields loads the pod through Pods' own API, pods-get-fields reads a post's values, and pods-update-fields writes them. Meta values are snapshotted on the post; table rows are snapshotted as a row image, so an inserted row is removed again and a changed row returns exactly. Writes cover simple field types with one scalar value. Relationship, file and repeatable fields are listed and read, but a write refuses them rather than leaving Pods' stores out of step. Writes are off until a site opts in.

Get the free plugin Read the docs

plugin-data-readplugin-data-write

What your AI can do

Real Pods operations, every write reversible.

List Pods fields for a post type pod
Read a post's field values from meta or table storage
Write simple field values (opt-in), snapshotted and reversible
Refuse relationship, file and repeatable field writes cleanly

Example prompts

Just ask.

What fields does the Book pod have?

Read the ISBN and page count on book 55.

Set the publisher field on these books to "Acme Press".

Under the hood

The real calls.

wpmcp, pods

plugin-data-read({ operation: "pods-get-fields", args: { post_id: 55, keys: ["isbn"] } })

plugin-data-write({ operation: "pods-update-fields", args: { post_id: 55, fields: { publisher: "Acme Press" } } }), opt-in; snapshotted

Frequently asked

Questions, answered.

Why can't it write relationship fields?

Pods keeps those values across post meta and its relationship table. Writing one store without the other would leave them out of step, so the write refuses instead.

How do I turn writes on?

With the wpmcp_enable_pods_write filter.

More integrations