MCP server for Axtolab AI Connector for WordPress — safely manage WordPress content from Claude, ChatGPT, and MCP-compatible AI clients.
28 tools with consistent naming (verb_noun pattern: wp_*) and descriptions present for all. However, parameter descriptions are sparse or missing for many tools. Input schemas visible but lack depth, most parameters have type but minimal constraint documentation (no min/max, format specs, or dependency notes). Output schemas not documented. Error handling guidance absent. Consent policy mechanism is sophisticated but not surfaced in tool descriptions. Baseline: 194 chars avg description; this server averages ~120 chars, below median. No examples of LLM-optimized descriptions (50-200 chars with WHEN/WHY context).
Regenerate multiple images in posts or pages.
Add a new WordPress site connection by decoding a connection token from the WordPress plugin admin UI.
Create a new draft post or page.
Delete a brand kit configuration.
Delete a comment.
Permanently delete a post or page.
Delete a menu item.
Output schemas not documented. Tools return data but LLMs cannot plan downstream calls or extract fields reliably. E.g., wp_get_changelog returns 'recorded changes' but structure is opaque.
Parameter descriptions sparse or generic. 'token' in wp_connect_site lacks format/length guidance. 'query' in wp_find_media_file lacks examples of valid search syntax. LLMs cannot infer constraints.
Confirmation tokens required for destructive/sensitive operations (publish, delete, price updates) but mechanism not explained in tool descriptions. LLMs will not know how to obtain tokens or why they're needed.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
Delete a custom field (post meta) from a post.
Delete a taxonomy term (category, tag, etc.).
Delete a custom field (term meta) from a taxonomy term.
Search for media files in the session image store by filename or path.
Generate an image using AI and insert it into a post or page.
List recorded changes captured by the AI Connector changelog: posts/pages/options/menus/etc. that were created, updated, trashed, restored or published by AI tool calls. Use to review what's happened in the current session, find a specific change to undo, or audit recent activity. Filter by session_id, target_type (post/option/menu/etc.), target_id, tool_name, action, status (rolled_back / pending), or since (ISO 8601 datetime). Snapshots are excluded from this list — call wp_get_change with a row id for the full before/after diff.
Return the capability groups, named preset, and tool list available to the current AI connection. Use this to know up-front what you're allowed to do (e.g. whether publishing or trash/restore are enabled) instead of discovering by trial-and-error.
List all connected WordPress sites.
Publish a post or page to live status.
Restore a trashed post or page.
Restore a previous revision of a post or page.
Set or remove the featured image for a post or page.
Get site and capability metadata.
Switch the active WordPress site connection.
Move a post or page to trash.
Update the title, content, or metadata of a post or page.
Update media metadata (alt text, title, description).
Upload media to WordPress from a local file path.
Update prices for multiple WooCommerce products.
Create a WooCommerce coupon code.
Update the price of a WooCommerce product.
No error handling guidance. Tools do not document what errors are retryable, user-fixable, or fatal. E.g., wp_connect_site may fail if token is invalid, but no recovery hint provided.
Numeric parameters lack min/max constraints. E.g., wp_woo_update_product_price accepts 'price' with no range validation hint. LLMs may pass negative or absurdly large values.