MCP Abilities - Toolset WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

Toolset abilities for MCP. Manage custom post types, fields, and relationships created with Toolset.

Tested up to: 7.0 Stable tag: 1.0.5 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html

Reader workflows

The 40 registered abilities form seven reader workflows:

• Content structures (8): inspect post types, their fields and taxonomies, list taxonomies, create or delete a custom post type, and create or delete a custom taxonomy.
• Content records and terms (8): create, inspect, list, query, update, trash, or permanently delete selected posts, and list or create taxonomy terms.
• Fields and field groups (5): inspect fields and field groups, create or update a field group, and create or update a field definition.
• Post relationships (5): inspect registered and post-specific relationships, create a relationship, link two selected posts, and retrieve related posts.
• Users and access (8): inspect Toolset user fields, users, roles, role capabilities, users by role, one user's capabilities, and the current user's access to a requested action.
• Toolset presentation controls (4): list Toolset forms and Views, inspect taxonomy editor controls, and select the taxonomy editor control for one post type.
• Migration audit and cleanup (2): audit active Toolset use across content and configuration, then preview or explicitly clean stale Toolset metadata, objects, and content attributes after a migration.

Authorization and change boundaries

• Every operation requires an authenticated WordPress user and the capability assigned to that operation. Content work requires the relevant edit or delete capability, taxonomy term creation requires manage_categories, user inspection requires list_users, and Toolset structure changes require manage_options.
• A post deletion targets one exact post. The default moves it to trash; permanent deletion happens only when the caller explicitly enables force.
• Deleting a Toolset post type processes every post of that type. Deleting a Toolset taxonomy deletes its terms. Both require the exact registered name and administrator permission.
• The stale-data cleanup defaults to a dry run. Its three mutation scopes default to off, the caller must enable each intended scope, and every run has an explicit bounded limit.
• Relationship changes require an exact relationship and exact post IDs. Field, group, post type, taxonomy, and taxonomy editor changes require their exact source-owned identifiers.
• The audit is read-only and reports content markers, metadata markers, and Toolset configuration objects so cleanup can be based on observed use rather than assumption.

Download MCP Abilities - Toolset

What It Does

Toolset abilities for MCP. Manage custom post types, fields, and relationships created with Toolset.

This plugin is part of the MCP abilities ecosystem. It gives an MCP-capable agent a focused, authenticated way to work with Toolset work inside WordPress through MCP.

Example: "Handle this WordPress maintenance task directly." - The agent can inspect the site, call the relevant ability, and return the result without making the human click through wp-admin for every step.

The Real Workflow

In practice, the human should not have to memorize every ability name.

The normal pattern is:

1. install the base MCP stack
2. install only the add-ons the site actually needs
3. let the agent discover the available abilities
4. give the agent a clear task with boundaries
5. verify the result in WordPress

The human's job is mostly to describe the goal. The agent's job is to figure out the mechanics.

Why This Feels Different

Most WordPress automation still leaves the repetitive part to the human.

This plugin is different because the agent can act inside the site through a narrow, authenticated ability surface:

• inspect current site state before changing anything
• run the specific action needed for the task
• return structured results that are easy to verify
• keep the workflow inside WordPress instead of a separate checklist

That changes the experience from:

• Here is what you should do in wp-admin

to:

• Tell the agent what needs doing, and let it carry out the work

Before vs After

Before

• ask the AI what to do
• copy the answer into WordPress by hand
• click through wp-admin for the repetitive bits
• postpone maintenance because the task is tedious

After

• tell the agent what needs doing
• let it inspect the relevant WordPress state
• let it run the targeted ability
• verify the result and move on

Who It Is For

This is a good fit for:

• agencies managing WordPress sites with AI-assisted maintenance
• operators who want agents to do real WordPress work instead of producing instructions
• teams already using MCP Expose Abilities
• sites where this WordPress area is updated often enough to deserve automation

It is especially useful when the manual version is repetitive enough that important maintenance gets delayed.

Documentation

Start with the main plugin page and base stack documentation:

• MCP Expose Abilities
• Plugin page
• Getting Started
• Install Order and Dependencies

If you are using an AI agent, the simplest instruction is often just:

• Read https://github.com/bjornfix/mcp-expose-abilities and figure out the stack before making changes.

Start Here

If you are new to the stack, use this order:

1. Install Abilities API.
2. Install MCP Adapter.
3. Install MCP Expose Abilities.
4. Install MCP Abilities - Toolset.
5. Confirm the new abilities appear in discovery.
6. Give the agent a clear task that uses this add-on.

If you skip base-stack verification and start with add-ons immediately, troubleshooting gets harder than it needs to be.

Abilities (40)

Usage Examples

List Toolset post types

{
  "ability_name": "toolset/list-post-types",
  "parameters": {}
}

Create a post with Toolset fields

{
  "ability_name": "toolset/create-post",
  "parameters": {
    "post_type": "issue",
    "title": "Broken checkout button",
    "status": "publish",
    "fields": {
      "wpcf-priority": "high"
    }
  }
}

Create relationship link

{
  "ability_name": "toolset/add-post-relationship",
  "parameters": {
    "relationship_slug": "project-to-issue",
    "parent_id": 101,
    "child_id": 205
  }
}

Changelog

1.0.5

• Fixed: Use the WordPress core user ability category for all user and role abilities.

1.0.4

• Update tested WordPress version metadata for Plugin Check.
• Align public release identity with the Basicus author/contributor rule.

1.0.3

• Added: toolset/cleanup-stale-data destructive cleanup ability for stale Toolset metadata, Toolset objects, and toolsetDSVersion content attributes after migration

1.0.2

• Added: toolset/audit-usage read-only ability to find posts/pages with Toolset blocks, shortcodes, fields, Views/templates, and Toolset configuration objects

1.0.1

• Fixed: Removed hard plugin header dependency on abilities-api to avoid slug-mismatch activation blocking
• Updated: Plugin URI to the bjornfix GitHub repository

1.0.0

• Initial release
• Post types: list, get fields, get taxonomies
• Posts: create, get, list, update, delete
• Issue tracker: create, list, update status

Contributing

PRs welcome. Keep changes focused on the plugin's WordPress ability surface and preserve authenticated, explicit workflows.

License

GPL-2.0+

Author

basicus

Links

• Plugin Page
• MCP Expose Abilities
• GitHub Releases

Star and Share

If this plugin saves you time or makes WordPress maintenance easier to verify, please:

• star the repo
• share it with people running WordPress sites
• point them to the main plugin page so they can see what the ecosystem can actually do

Why do it?

Because agent-friendly open WordPress tooling helps more of the boring but important work get done.