Get the plugin
WP MCP/Integrations/Custom fields

Custom fields integration

Pods MCP

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.

plugin-data-readplugin-data-write

In practice

How Pods work goes with an agent.

Pods lets each pod decide where its values live: in ordinary post meta, or in a table of the pod's own with one row per post. The right place to read or write depends on that choice, and a naive meta write on a table pod would go nowhere. WP MCP asks Pods' own API which storage the pod uses, then reads or writes the right one. Field definitions are available for post type pods. Writes are limited to simple single-value fields and stay off until a site turns them on.

What fields does the Book pod have, and which of them can you write?

Runs pods-list-fields with post_type book. It returns each field's name, label and type, a writable flag, and the pod's storage, meta or table. Read only.

Read the ISBN and page count on book 55.

Runs pods-get-fields with post_id 55 and keys isbn and pages. It reads from post meta or from the pod's table row, depending on the storage. Nothing is written.

Set the publisher to Acme Press on these twelve books.

Runs pods-update-fields once per post, only when the site has opted in with wpmcp_enable_pods_write. Meta values are snapshotted on the post, and table rows as a row image, so rollback-session undoes all twelve.

Which authors are attached to book 55?

Runs pods-get-fields for the relationship field. Relationship fields are listed and read, with every stored value returned, but pods-update-fields refuses to write them.

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

Example Pods prompts.

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 Pods calls, under the hood.

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

Safety and access

What can be undone on Pods, and what costs what.

Recoverable on Pods

  • For a meta pod, the post is snapshotted before the write and rollback-operation restores its meta.
  • For a table pod, the pod's row is snapshotted as a row image: a changed row returns exactly, and a row the write inserted is removed.
  • A session of many writes is undone together with rollback-session.

Pods limits and opt-ins

  • pods-update-fields is off until the wpmcp_enable_pods_write filter returns true.
  • Writable types: text, paragraph, wysiwyg, code, password, slug, email, phone, website, color, number, currency, date, datetime, time, boolean and oembed. Repeatable fields are not writable.
  • Relationship, file, avatar, taxonomy, comment and author fields can be read but not written.
  • Only post type pods are supported. Taxonomy, user and other pod types answer that there is no pod.

Free or Pro: The Pods integration is free, reads and writes alike. It runs on the plugin-data pair as plugin-data-read and plugin-data-write, so it adds no extra tools. The reads work as soon as Pods is active. The one write, pods-update-fields, is opt-in through the wpmcp_enable_pods_write filter, and every write needs permission to edit the post it targets. Pro adds no extra Pods operations.

In the free plugin

The Pods integration is in the free plugin.

The core Pods tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.

Frequently asked

Pods MCP: 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.

In Pods, how do I turn writes on?

With the wpmcp_enable_pods_write filter.

How does it know whether a pod uses meta or a table?

It loads the pod through Pods' own API and reads the pod's storage setting. If Pods is running in tableless mode, values are treated as meta. The storage is returned in every pods-list-fields and pods-get-fields response, so the agent always knows where a value came from.

Does it work with Pods for taxonomies or users?

No, only with pods that extend a post type. For any other pod type, the operations answer with a clear no-pod message rather than guessing a storage location. Custom post types extended by a pod, and the post meta behind them, are covered as described above.

Are boolean and date values converted?

Booleans are saved as 1 or 0. Everything else goes to the field as given, so the agent should pass dates in the format Pods stores for that field. The response reads the value back from storage after the write, so a mismatch is visible straight away.

Point your AI at Pods.