About this plugin
Corsen Context publishes a bounded overview of selected public WordPress content and provides four core read-only content tools through a JSON-RPC endpoint. Five further extension tools are opt-in and owner-controlled: get_product (live price, stock, images and variants via WooCommerce, plus an agentPurchase policy the agent must respect), get_sections (a page outline plus one bounded section per call), get_structured_data (typed JSON-LD blocks), check_agent_access (reads the result of the owner’s latest agent-access self-test) and request_expert_call (a human-only expert intake, annotated readOnlyHint:false and refused server-side for AI callers with error code human_only). 1.5.0 also registers the enabled tools through the experimental WebMCP browser API when the site owner opts in and the browser exposes that API, and through the WordPress Abilities API on WordPress 6.9 or newer. What it does The plugin provides three separate surfaces: Static Layer — Generates /llms.txt with a structured overview of selected public content. An optional, bounded /llms-full.txt export can be enabled in settings. Dynamic Layer — Exposes the enabled tools through a Model Context Protocol (MCP) JSON-RPC endpoint at the canonical URL generated by WordPress. The four core tools and four WordPress read extensions are read-only; the optional human-only expert intake is explicitly non-read-only and refuses agent calls server-side. The endpoint targets protocol version 2025-11-25 with JSON responses and no server-sent event stream. In-Page Layer (opt-in) — Registers the enabled tools through WebMCP document.modelContext , including explicit per-tool annotations. Serving the bridge does not enable WebMCP in every browser: a compatible browser/client and, where applicable, current trial enrollment or a development flag are also required. Key Features Default surfaces — /llms.txt and the public read-only endpoint are enabled; the heavier /llms-full.txt export and WebMCP bridge are opt-in. MCP 2025-11-25 target — Supports initialize , ping , tools/list , tools/call , resources/list , resources/read , and notifications/initialized . The endpoint returns JSON responses and does not provide server-sent event streaming. 4 core read-only tools — search_site , get_page_content , list_content , get_sitemap ; every other surface tool is an opt-in extension, off by default. SEO integration — Reads Yoast SEO and Rank Math metadata for better descriptions. Request controls — Rate limiting, strict input validation, same-site content URL checks, defensive MCP response headers, and optional API-key authentication. Admin settings page — Choose public post types, exclude paths, set rate limits, toggle surfaces, and select any subset of the tools. Control Center (Settings > Corsen Context Control) — one card per surface and tool, honest exposed/needs-config/off badges, what-agents-see preview, and a bounded local audit log with a one-click purge. Dashboard widget — See your AI context status at a glance. Bounded generation — Total item and output-byte limits protect the optional full-content export. Content safety — Drafts, private posts, password-protected posts, excluded paths, and content vetoed by the exposure filter are not served. Credit line — “Powered by Corsen Context” in generated files (configurable). Published Endpoints and Discovery Hints When the corresponding settings are enabled, Corsen Context publishes: robots.txt — An MCP: line containing the canonical endpoint URL generated by WordPress llms.txt — When MCP is enabled, the generated file includes its canonical endpoint URL; the separate promotional credit remains optional HTML head — <link rel="mcp"> link element added automatically Direct URL — /llms.txt remains available to clients that know the convention These are project discovery hints, not universally consumed standards. They do not guarantee that a search engine or client will discover or use the endpoint. Requirements WordPress 6.0 or higher PHP 8.0 or higher A web-server configuration that routes the published /llms.txt path to WordPress. Pretty permalinks are recommended for this static path. The MCP REST endpoint itself uses WordPress’s canonical URL and can use the ?rest_route=/corsen-context/v1/mcp form with Plain permalinks. WebMCP additionally needs a browser and agent/client that implement the evolving API. Chrome’s development flag and public origin-trial path can change; follow the current browser setup guide . Part of a Bigger Ecosystem Corsen Context is an open-source project by Corsen AI . The project also provides TypeScript packages for Node.js, Next.js, and Astro, plus a reference Express server. WordPress uses this dedicated PHP plugin. GitHub Repository Full Documentation