Connecting via WordPress Abilities

On WordPress 6.9 and newer, SchemaWP 1.2.0 registers its tools as WordPress Abilities — the standard, plugin-neutral way for WordPress to expose capabilities to AI agents. Hosts like Novamira or the official WordPress MCP Adapter can then discover and run SchemaWP’s tools alongside their own, with no SchemaWP Application Password or Agent API token required — authentication is handled by the host and WordPress itself.

Requires WordPress 6.9+. On older versions the Abilities option is hidden on the Connections page — use the MCP or API method instead (both work on WordPress 6.7+).

Via Novamira (recommended)

1. Install and activate Novamira on your site — it bundles the WordPress MCP Adapter and an Abilities Hub
2. Keep SchemaWP’s agent connection switch enabled (Connections page sidebar) — SchemaWP registers its abilities automatically
3. Open Novamira’s Abilities Hub and confirm SchemaWP abilities appear under categories like SchemaWP Utility (includes schemawp/bootstrap), SchemaWP ACSS, Kits, and Patterns
4. Connect your AI client (Claude, Cursor, etc.) following Novamira’s own connect flow — agents can then discover and run SchemaWP abilities alongside Novamira’s tools

Via the WordPress MCP Adapter

1. Activate the official WordPress MCP Adapter plugin (or any host that bundles it)
2. Leave SchemaWP agentic access enabled — SchemaWP marks its abilities mcp.public, so the adapter’s default server discovers them via mcp-adapter-discover-abilities and runs them via mcp-adapter-execute-ability
3. Point your MCP client at the adapter’s WordPress MCP endpoint (see the adapter docs) and authenticate as a user with manage_options

Note: this path uses the WordPress Abilities + MCP Adapter stack, not SchemaWP’s own OAuth MCP server. If you want SchemaWP’s dedicated OAuth / App Password MCP endpoint, use the MCP connection method instead.

Agent session workflow

However the agent reaches the abilities, it should follow the same session order as MCP:

1. Call schemawp/bootstrap once at session start — it returns core_rules (the same briefing MCP delivers on initialize.instructions) plus the required workflow. If bootstrap is skipped, call schemawp/acss-get-instructions instead
2. Discover abilities and their input_schema from the abilities list endpoint (/wp-json/wp-abilities/v1/abilities) or the host UI; if a catalog is truncated, call schemawp/acss-get-tool-schema
3. Before any writes: run schemawp/acss-get-site-context and schemawp/acss-get-history, then load skills and read config the same way as on MCP

The Connections page also offers an optional pasteable brief for chat clients, so the agent follows this workflow without extra prompting. Mutating calls are audited in Patch History, exactly like MCP.