Zinn® SEO abilities reference

Endpoints

https://example.com/wp-json/zinn-seo/v1/mcp

wp mcp-adapter serve --server=zinn-seo --user=<login>

/wp-json/wp-abilities/v1/abilities?category=zinn-seo

/wp-json/wp-abilities/v1/abilities/<name>/run

Authentication and permissions

HTTP requests authenticate with a WordPress application password (HTTP Basic). Connecting to the MCP server needs the capability shown below; every ability then checks its own permission, per object. Read-only abilities run with GET and their input in the query string; the others with POST and a JSON body {"input": {…}}.

Examples

# REST: run an ability
curl -u your-username:your-application-password \
  "https://example.com/wp-json/wp-abilities/v1/abilities/zinn-seo/export-settings/run"

# MCP (JSON-RPC over HTTP, after "initialize")
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"zinn-seo-export-settings","arguments":{}}}

WP-CLI commands

Run these on the server with WP-CLI. Each command checks the same permissions as the plugin's screens; the examples are taken from the plugin's own help text.

Actions and filters

Every hook the plugin offers, with the description from its source code. Filters change a value; actions let you run code at a moment; entry points are actions you fire to ask the plugin to do something.