Appearance
MCP and abilities
VX Modules does not serve MCP and does not configure it. VX Framework does both: it serves the endpoint at /wp-json/vx/mcp, and its AI settings screen turns it on, decides how much to expose, and writes the setup for whichever agent you use, application password and all.
Two screens configuring one endpoint could only disagree, so there is only one.
What VX Modules adds is abilities, registered with WordPress's own abilities registry — which is what that endpoint hands out.
The MCP screen
VX Modules → MCP is a report. It lists every ability the plugin offers, says whether it is currently reaching the endpoint, and links to VX's own AI settings screen. It changes nothing itself.
The item only appears while VX's MCP surface is available.
What decides whether they arrive
Two things, and both have to be right.
1 · VX's exposure level
VX's exposure levels one through three cover VX's own abilities and WordPress core's. A third party's abilities reach the endpoint only under Full access, or under Custom when ticked individually.
2 · The module has to be on
A module that is off registers none of its abilities. Turn the Forms module off and the form abilities disappear from the endpoint along with the rest of it.
The abilities
Modules
| Ability | What it does |
|---|---|
vxm/list-modules | Which modules exist and which are on |
vxm/set-module | Turn one on or off |
Forms
| Ability | What it does |
|---|---|
vxm/list-forms | Every form |
vxm/get-form | One form in full |
vxm/create-form | Create a form |
vxm/save-form | Save a form |
vxm/duplicate-form | Copy a form |
vxm/delete-form | Delete a form |
vxm/list-entries | Entries, filtered |
vxm/get-entry | One entry |
Columns and bulk edit
| Ability | What it does |
|---|---|
vxm/get-columns | What a post type's list screen shows |
vxm/save-columns | Set it |
vxm/bulk-spec | What can be bulk edited, and how |
vxm/bulk-edit | Edit one field across many posts |
vxm/bulk-edit previews by default: it reports what each post would become before anything changes. An agent has to ask for the write explicitly.
The Sheet
| Ability | What it does |
|---|---|
vxm/list-sheet-types | Which post types have a sheet |
vxm/query-rows | Read a post type's field values as rows |
vxm/save-row | Write one row back, through VX's validation |
Validation
| Ability | What it does |
|---|---|
vxm/get-validation | The rules a post type enforces |
vxm/save-validation | Set them |
vxm/check-validation | Test values against them |
Importing
| Ability | What it does |
|---|---|
vxm/list-import-sources | What can be imported from ACF, Meta Box, or Pods |
vxm/plan-import | Plan a migration |
vxm/run-import | Run it |
Safety
Every write goes through the same path a human's would: VX's runtime, VX's validation, and your validation rules. An agent cannot write a value the Sheet would refuse.
What an agent writes is not checked at an editor, though, because it never passes one — so anything an agent publishes against a rule is checked after the fact and listed on the dashboard. That list is worth a glance on any site where an agent has write access.