Voxel theme — listings and their fields, categories, orders and memberships, reviews, messages and the search index.
Voxel publishes no API of its own and keeps its post types out of the WordPress one. Without this, an assistant on a Voxel site can touch everything except what makes it a Voxel site.
Create and edit listings through Voxel's own validation — location, gallery, work hours, relations.
Field keys, types and taxonomies are read from your install, never guessed.
Query the index that understands radius, price and availability — things WP_Query cannot answer.
Read orders, change their status, and manage plans and paid-listing packages.
Timeline posts, replies and direct messages, with the privacy caveats stated plainly.
Every destructive action sits behind a separate permission a normal connection never gets.
Ask in plain language and the Voxel integration turns it into typed calls against Voxel's own models — no exports, no SQL, no brittle scripts.
Define post types and fields, then seed real listings without touching a form.
Fill a missing field across every listing at once.
Find listings with gaps, stale hours or missing photos, and fix them in place.
Chain Voxel actions into multi-step workflows your team can reuse.
The NibWP Voxel integration exposes a Voxel directory to any MCP-compatible AI agent — Claude, Cursor, Claude Code or your own — as typed, schema-validated tools. Instead of filling in submission forms or writing custom queries, you describe what you want in plain language and the agent reads and writes real Voxel data over the Model Context Protocol (MCP).
This matters more for Voxel than for most themes. Voxel keeps its post types in a JSON option, spreads field values across typed meta and several custom tables, and publishes no REST API of its own — so ordinary tools reach almost nothing that makes the site a directory. NibWP works through Voxel’s own models, which means listings, fields, taxonomies, orders, memberships, reviews and the geographic search index are all available, with writes validated exactly as the front-end form would validate them.
It runs on the NibWP Pro plan and activates the moment Voxel is detected, with scoped tokens, an approval screen and an audit log so automation stays safe. Pair it with Voxel Pro to build the templates your directory renders with, or browse all NibWP integrations.
| Tool | Type | What it does |
|---|---|---|
| nibwp/voxel-info | read | Version, modules, post types and index health. |
| nibwp/voxel-post-types | read | Every post type with its real field and filter vocabulary. |
| nibwp/voxel-posts | read | Search through Voxel's index — radius, price, availability. |
| nibwp/voxel-render | read | Evaluate Voxel dynamic tags. |
| nibwp/voxel-posts-write | write | Create and update listings through Voxel's own validation. |
| nibwp/voxel-terms | write | Categories and their terms. |
| nibwp/voxel-orders | write | Orders and their status. |
| nibwp/voxel-plans | write | Membership plans and paid-listing packages. |
| nibwp/voxel-timeline | write | Reviews, posts and replies. |
| nibwp/voxel-messages | write | Direct messages and notifications. |
| nibwp/voxel-templates | write | Which template fills which slot. |
| nibwp/voxel-schema | destructive | Edit post type and taxonomy definitions. |
| nibwp/voxel-delete | destructive | Trash, restore and permanently delete. |
Yes. Once the Voxel theme is active, NibWP detects it automatically and the Voxel abilities go live in your connected AI client — no configuration needed.
Voxel publishes no REST API of its own, and holds its post types out of the WordPress one unless you switch them on per type. Without this integration an assistant can edit ordinary posts and almost nothing that makes the site a Voxel site.
Both. Writes go through Voxel's own sanitise, validate and update steps, and the search index is refreshed afterwards so the listing is findable straight away.
Nothing is written. Writes are all-or-nothing, and the response names each field that failed — a half-written listing is worse than a refusal.
Deletes live behind a separate permission that an ordinary read-and-write connection is never granted. Trashing is preferred over permanent deletion, and a trashed listing is removed from the search index first so the site does not serve results that 404.
No. Editing the data model sits behind the same elevated permission as deleting, and every schema change previews the difference first, backs up the previous configuration, and can be rolled back.
Yes — membership plans, paid-listing packages and orders are all covered. Changing an order status updates the record in Voxel; it does not move money at your payment provider.
No. The integration works on the Pro plan and handles your data. Voxel Pro is the separate add-on that builds your templates — cards, listing pages, archives and search pages.
Activate the integration and it's live on your MCP endpoint instantly.