Jono Alderson

Manage your website’s <code>.well-known</code> files with ease using this powerful yet simple plugin. The Well-Known File Manager provides a user-friendly interface to create, edit and manage standardized <code>.well-known</code> files – essential components for modern web security, app associations, and service discovery.
Whether you need to implement security.txt for vulnerability reporting, configure app associations, or set up protocol handlers, this plugin handles the technical complexities while giving you complete control. It creates actual files on your server for maximum compatibility and performance, without requiring any special server configuration or technical knowledge.
Perfect for developers, site owners, and administrators who want a reliable way to manage their site’s <code>.well-known</code> directory through a clean, intuitive WordPress interface.
Key Features:
<ul>
<li>Easy Management: Simple toggle switches to enable/disable <code>.well-known</code> files</li>
<li>Physical File Creation: Creates actual files in the <code>.well-known</code> directory for maximum compatibility</li>
<li>Content Editing: Built-in content editor for each file type with syntax highlighting</li>
<li>Default Templates: Pre-configured templates for common <code>.well-known</code> files</li>
<li>Validation: Content validation to ensure files meet required standards</li>
<li>Priority Files: Highlighted support for important files like <code>security.txt</code>, <code>assetlinks.json</code>, and <code>apple-app-site-association</code></li>
<li>Automatic Cleanup: Removes files when disabled to keep your server clean</li>
<li>Data Preservation: Files and settings are preserved when the plugin is deactivated or uninstalled</li>
</ul>
Supported Files:
<ul>
<li>Security Files: <code>security.txt</code>, <code>security-txt</code></li>
<li>App Associations: <code>assetlinks.json</code>, <code>apple-app-site-association</code></li>
<li>Protocol Handlers: <code>change-password</code>, <code>gpc</code>, <code>hoba</code></li>
<li>Discovery: <code>host-meta</code>, <code>host-meta.json</code>, <code>nodeinfo</code></li>
<li>Authentication: <code>openid-configuration</code>, <code>oauth-authorization-server</code></li>
<li>And many more…</li>
</ul>
How It Works:
This plugin takes a physical file approach rather than routing requests through WordPress:
<ul>
<li>When Enabled: Creates actual files in your <code>.well-known</code> directory</li>
<li>When Disabled: Removes the files from your server</li>
<li>No Server Configuration: Works on any hosting setup without requiring <code>.htaccess</code> modifications</li>
<li>Maximum Compatibility: Files are served directly by your web server for optimal performance</li>
</ul>
Benefits:
<ul>
<li>Universal Compatibility: Works on any hosting provider without special configuration</li>
<li>Better Performance: Files are served directly by the web server, not through WordPress</li>
<li>Simplified Setup: No need to configure rewrite rules or server settings</li>
<li>Automatic Management: Files are created and removed automatically based on your settings</li>
<li>Clean Server: Disabled files are completely removed from your server</li>
<li>Data Safety: Your files and settings remain intact when deactivating or uninstalling the plugin</li>
</ul>

Well-Known File Manager

Manage files in the .well-known directory with ease.

Kevin Pirnie

AI agents — tools like ChatGPT, Claude, Copilot, and the growing ecosystem of autonomous AI systems — are increasingly being pointed at websites to gather information, interact with APIs, and perform tasks on behalf of users. For a site to work well with these agents, it needs to speak the right language: publishing structured discovery files, declaring its capabilities, and responding to agent-specific requests in the right format.
KP Agent Ready handles all of that for your WordPress site. It implements the current set of agent-readiness standards and the broader AI agent ecosystem — without requiring you to manually create files, edit server configs, or touch a line of code. Everything is managed from a dedicated settings page in the WordPress admin.
<h4>What It Does</h4>
RFC 8288 Link Response Headers 
Every response your site sends will include <code>Link</code> headers pointing agents to your API catalog, agent skills index, and MCP server card. This is how agents find your discovery documents without having to guess URLs.
API Catalog — <code>/.well-known/api-catalog</code> 
Publishes a machine-readable catalog of your site’s APIs in the <code>application/linkset+json</code> format defined by RFC 9727. Each entry in the catalog can point to an OpenAPI specification, human-readable documentation, and a health/status endpoint. If you have not configured any entries yet, the plugin serves a sensible fallback automatically so the endpoint is always valid.
Agent Skills Index — <code>/.well-known/agent-skills/index.json</code> 
Publishes a skills discovery index per the Agent Skills Discovery RFC v0.2.0. This tells agents what your site can do — search your blog, browse your portfolio, submit a contact form, and so on.
Skills are built from three sources:
<ul>
<li>Blog articles — a search skill and a browse skill, toggled with a single switch</li>
<li>Custom post types — any public CPT registered on your site appears as a checkbox; tick it and it gets a browse skill pointing to its archive</li>
<li>Manual entries — define any additional skill with a name, type, description, URL, and an optional sha256 digest</li>
</ul>
MCP Server Card — <code>/.well-known/mcp/server-card.json</code> 
Publishes an MCP Server Card (SEP-1649) identifying your site to Model Context Protocol clients. Configurable name, version, description, transport endpoint, and a capability list. If you do not have an MCP server running yet, just leave the transport blank — the card is still valid and useful for discovery.
OAuth / OIDC Discovery — <code>/.well-known/openid-configuration</code> or <code>/.well-known/oauth-authorization-server</code> 
If your site exposes protected APIs that require authentication, this feature publishes the discovery metadata agents need to authenticate. Supports both OpenID Connect Discovery 1.0 and RFC 8414. Disabled by default — only enable it if you have the infrastructure in place.
OAuth Protected Resource Metadata — <code>/.well-known/oauth-protected-resource</code> 
Complements the OAuth/OIDC feature by publishing RFC 9728 Protected Resource Metadata. Disabled by default.
robots.txt Content Signals 
Appends Content Signals directives to your <code>robots.txt</code> file, declaring your preferences for how AI systems may use your content:
<ul>
<li>ai-train — whether AI companies may use your content to train models</li>
<li>search — whether search engines may index your content</li>
<li>ai-input — whether AI retrieval systems (RAG) may use your content as input</li>
</ul>
Markdown Negotiation 
When an AI agent sends a request with the <code>Accept: text/markdown</code> header, the plugin intercepts the response for singular posts and pages and returns a clean Markdown version of the content. Regular browser requests are completely unaffected.
WebMCP 
Injects a small JavaScript snippet into your page footer that calls <code>navigator.modelContext.provideContext()</code>, exposing your site’s key actions as tools to AI agents running in the browser. Built-in tools include blog search, portfolio navigation, and contact page navigation — each individually toggleable.
llms.txt and llms-full.txt 
Generates physical <code>/llms.txt</code> and <code>/llms-full.txt</code> files in your WordPress web root per the <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a> specification. These files give AI systems a structured, readable index of your site’s content — who you are, what pages exist, and what your posts are about.
<pre><code>llms.txt contains your site header and a clean list of links by content type. `llms-full.txt` contains the same structure but expands each entry with an excerpt or truncated content block so AI systems can understand the content without fetching every URL.
</code></pre>
Files are regenerated automatically when posts are published, unpublished, or trashed, and whenever settings are saved. A manual Regenerate button is available in the llms.txt settings tab. If your host prevents direct file writes, the generated content is displayed in the admin as a copyable textarea so you can create the files manually.
Configurable options include a custom intro block, toggling pages and posts independently, selecting additional custom post types, setting the excerpt word limit for <code>llms-full.txt</code>, and defining optional additional links that appear under an <code>## Optional</code> section in both files.
<h4>Developer Filters</h4>
Two filters let themes and other plugins extend the plugin’s output without touching settings:
<pre><code>kp_agent_skills — add entries to the agent skills index:

add_filter( 'kp_agent_skills', function ( array $skills ): array {
 $skills[] = [
 'name' => 'my-skill',
 'type' => 'api',
 'description' => 'Does something useful.',
 'url' => 'https://yoursite.com/api/endpoint',
 ];
 return $skills;
} );

kp_webmcp_tools — add tools to the WebMCP context:

add_filter( 'kp_webmcp_tools', function ( array $tools ): array {
 // $tools is the PHP array that becomes the JS tools array
 return $tools;
} );
</code></pre>

KP Agent Ready

Very good for AI

Make your WordPress site discoverable and usable by AI agents via well-known endpoints, MCP, OAuth, and Markdown negotiation.

Well-Known File Manager vs KP Agent Ready