by
corsenai
0 (0 reviews)
Corsen Context
Owner-controlled AI access to your public content: llms.txt, a read-only MCP endpoint, and opt-in WebMCP tools for agents in the browser.
Corsen Context ranks #16,649 among WordPress.org plugins with 100+ active installations, and was last updated Oct 23, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.5.18
Current Version v1.5.18
Updated 2 weeks ago
Last Update on 23 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Top 25% by installs
Downloads -62.2% this week
Actively maintained
Rank
#16,649
—
No change
Active Installs
100+
—
No change
KW Avg Position
122.5
1.5 worse
Downloads
1.8K
+3 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 200
100+
200+
3,975
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 92 more installs to reach 200+
Rank Changes
Current
#16,649
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Security History
Source: WPVulnerabilityNo known vulnerabilities on record for Corsen Context. Checked 1 month ago.
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.5.18
- Last Updated
- Oct 23, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 8.0 or higher
- Author
- corsenai
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners who want their content accessible to AI agents like Claude, ChatGPT, Cursor, and Grok. It solves the problem of AI agents being unable to understand and access site content by generating llms.txt files and exposing an MCP server with tools to search, read, and list site content.
- Generates llms.txt and llms-full.txt
- MCP server with 4 tools
- search_site, get_page_content, list_content, get_sitemap
- Yoast SEO and Rank Math integration
- Rate limiting and SSRF protection
- Admin settings page
- Dashboard widget
- Smart caching via transients
Frequently Asked Questions
Common questions about Corsen Context
MCP (Model Context Protocol) lets an AI client outside the page call your site's tools over HTTP. WebMCP is the browser-side counterpart: the page registers tools with document.modelContext, and an agent running inside the browser calls them. Corsen Context serves the same read-only tools on both; WebMCP adds no write access and no new data.
Model Context Protocol is an open protocol for communication between AI applications and external systems. Corsen Context targets the 2025-11-25 protocol version for its read-only JSON-RPC endpoint.
A proposed convention where websites place a /llms.txt file containing a structured Markdown overview. Support varies by client and search engine, so it should be treated as an additional publishing surface rather than an indexing guarantee.
The plugin limits output to selected public post types and rejects draft, pending, private, password-protected, trashed, or excluded content. Site owners can also veto individual posts with the corsen_context_can_expose_post filter. As with any public export, review the selected post types and exclusions before enabling it on a site with membership or conditional-visibility plugins.
When MCP is enabled, normal pages receive a small discovery link. When WebMCP is also enabled, the plugin emits an origin-trial meta tag if configured, a short inline configuration with the tool definitions, and one deferred script file that browsers cache. Generated metadata may use bounded WordPress transients for anonymous requests that carry no WordPress session cookie (consent, analytics or CDN cookies do not disable that cache). Rendered page content is not placed in the shared MCP cache, and /llms-full.txt uses item, byte, and generation-lock limits. Measure representative pages on your own hosting rather than assuming zero impact.
By default, Corsen Context reads stored public content without executing the_content, dynamic blocks, or shortcodes. This avoids accidentally exporting personalized output. Site owners can opt into full rendering with the corsen_context_render_mode filter; full-rendered output is never stored in the shared content cache. Compatibility depends on the page builder and should be tested on the site.
Yes. In Settings > Corsen Context you can: Choose which post types to include (pages, posts, products, custom types) Exclude specific URL paths Choose which tools MCP, WebMCP and the Abilities API advertise and allow (extension tools stay off until you enable them) Hide any tool from in-page (WebMCP) agents while keeping it available over MCP, per tool, from the Control Center or the settings page Disable MCP, llms.txt, or the entire plugin
The standard public product post type can be selected. The plugin exports its stored public content under the same rendering and exclusion rules as other post types. Themes, product add-ons, memberships, prices, variations, and dynamic shortcodes can change what a visitor sees, so test the required WooCommerce fields and visibility rules on the target site before claiming compatibility. When you enable it, the get_product extension tool additionally serves live price, sale, stock, image, and (for variable products) variant data through WooCommerce APIs; it requires WooCommerce to be active and the product post type to be selected.
You can set an API key by defining CORSEN_CONTEXT_API_KEY in your wp-config.php: define('CORSEN_CONTEXT_API_KEY', 'your-secret-key-here'); Server-side requests must then include X-MCP-Key: your-secret-key-here or Authorization: Bearer your-secret-key-here. The supplied WebMCP bridge intentionally sends no key, cookies, or visitor credentials. Do not embed the key in page source. Use either a public, read-only, rate-limited endpoint for WebMCP or a key-protected endpoint for configured server-side MCP clients with WebMCP disabled.
Enable WebMCP in Settings > Corsen Context, then use a browser and agent/client that implement the experimental API. Serving the registration script alone is not enough. For local Chrome testing, follow the current documented flag. For a public trial, enroll the exact HTTPS origin and use its current, unexpired token. See the browser setup and verification guide. An origin-trial token is delivered to browsers and is not an MCP credential. Successful registration also does not prove the endpoint or content policy: execute search_site, pass one result to get_page_content, and inspect the grounded answer.