Skip to content
Content Formats and Agent APIs

WordPress Abilities, MCP and Context Discovery

2 min read

citelayer® Free exposes its existing data through the WordPress Abilities API. To use those tools from an MCP client, connect a separate WordPress MCP Adapter and authenticated account.

Set up a safe connection

  1. Use WordPress 6.9+ and an up-to-date citelayer® Free installation.
  2. Install and configure the official WordPress MCP Adapter using its current connection documentation.
  3. Connect your client to the adapter’s transport with an authorized administrator account. Do not use context.json as the MCP server URL.
  4. Open citelayer® → WebMCP and confirm abilities are enabled and Read-only mode remains on.
  5. List the client’s tools and call get-compatibility-status before attempting other actions.

Seven read abilities

  • citelayer/get-readiness-score: cached dashboard scan and checks.
  • citelayer/get-llms-txt-status: index status and scope.
  • citelayer/get-bot-analytics: aggregate crawler activity.
  • citelayer/get-ai-blind-spots: pages without matching logged visits.
  • citelayer/get-referral-stats: recognized AI arrival signals.
  • citelayer/get-schema-status: schema configuration/status.
  • citelayer/get-compatibility-status: providers and API availability.

Two optional write abilities

citelayer/run-readiness-scan runs and stores a scan. citelayer/set-llms-txt-exclusion changes one post’s index exclusion. Both are absent from discovery while Read-only mode is on, and an attempted write is refused. Deliberately switch that mode off only when you want these actions.

Permissions and limits

All Free abilities require manage_options; exclusion also requires permission to edit the target post. Results are aggregated, not raw visitor/customer exports. Older WordPress versions do not register the abilities. These tools read citelayer data; they do not provide arbitrary site content or improve citation frequency by themselves.

Context discovery and add-on versions

/.well-known/mcp/context.json contains site/shop context and links. It is not a standalone MCP server or evidence of browser WebMCP tools. EDD 1.2.1 registers citelayer-edd/ status, feature-toggle and cache abilities through the Core Abilities API. These tools require WordPress 6.9+ and a separately configured MCP adapter; confirm that your installed add-on is up to date.

Connection documentation

Use the official MCP Adapter documentation for transport and authentication. Connection URLs and credentials belong to your site; never paste secrets into a public support request.

Next step

Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.

Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.