mcp-wordpress

MCP Discovery — WordPress Plugin v0.3.0

Exposes /.well-known/mcp-server on any WordPress site so AI agents can discover it via mcp://. Implements draft-serra-mcp-discovery-uri-03.

---

Once installed, your site exposes:

GET https://yoursite.com/.well-known/mcp-server

Which returns:

{
  "mcp_version": "2025-06-18",
  "name": "My Shop MCP Server",
  "endpoint": "https://yoursite.com/wp-json/mcp/v1",
  "transport": "http",
  "auth": { "type": "none" },
  "capabilities": ["tools", "resources"],
  "categories": ["e-commerce"],
  "languages": ["it"],
  "last_updated": "2026-03-25T00:00:00Z",
  "expires": "2026-09-25T00:00:00Z",
  "crawl": true
}

AI agents resolve mcp://yoursite.com and connect directly.

---

1. Download the mcp-discovery/ folder
2. Upload to /wp-content/plugins/
3. Activate in WordPress admin
4. Go to Settings → MCP Discovery
5. Verify at https://yoursite.com/.well-known/mcp-server

Or wait for approval on wordpress.org and install directly from Plugins → Add New → Search "MCP Discovery".

---

| Field | Default | Description | |---|---|---| | Server Name | Site name | Human-readable name | | Description | Site tagline | Natural language description | | MCP Endpoint URL | REST API base | URL of your MCP endpoint | | Authentication | None | none / apikey / oauth2 | | Categories | auto | Comma-separated (WooCommerce auto-detected) | | Contact Email | Admin email | Contact for the server | | Manifest Expiry | 90 days | How long before manifest is stale | | Allow Crawling | Yes | Opt-out of public indexing |

---

• Endpoint domain validation — endpoint MUST be on same domain or

subdomain. Invalid endpoints fall back to default REST API URL.

• Expires field — manifest declares its own expiry date.

---

Auto-detected. Adds `e-commerc