Site MCP: A Free WordPress MCP Server Plugin (2026)

Site MCP (listed as "Site MCP – Self-Hosted MCP Server for AI Assistants") is a free WordPress plugin that gives AI assistants and agents a read-only front door to your site through the Model Context Protocol (MCP). Instead of scraping your pages and guessing, an assistant connects to one address, searches your content, reads any page as clean Markdown and, if you run WooCommerce, looks up products with live prices and stock. We built it at 313 Automations and this page is its documentation: what it does, what it never shares, every setting, and why that matters for being cited by AI.

What does Site MCP do?

It runs a small MCP server inside WordPress. An AI client connects, reads the list of tools, and calls them with plain questions. Every tool is marked read-only, so an agent can look but never change anything, place an order or send a message. The six tools:

• get_site_info: site name, description, language, the main menu pages and whatever contact details you choose to share
• search_content: searches pages, posts and any public post type you switch on, with a short summary of each match, up to 10 at a time
• list_content: every shared page or post, 50 per page, so an agent can work through a whole site
• get_content: the full text of one page or post as Markdown, by address, path or ID, with headings, lists, tables and links kept and menus, scripts and forms dropped
• search_products (WooCommerce): find products by words, category, price range or stock, up to 20 at a time
• get_product (WooCommerce): price, sale price, availability, options and variations, description, rating and images, by ID, address, slug or SKU

Alongside the server it publishes two discovery files. The server card at /.well-known/mcp/server-card.json is what MCP directories and clients read to learn what your server offers. The llms.txt file lists your main pages, recent posts and product categories with a pointer to the server. If your site already has an llms.txt file, the plugin leaves it alone.

What is never shared

The rule is simple: the server shares only what a logged-out visitor can already see. Every tool, and the llms.txt file, checks each item against the same list before returning it:

• Unpublished work: drafts, private, scheduled and password-protected pages, posts and products
• Noindex content: anything marked noindex in Yoast SEO, Rank Math, SEOPress or The SEO Framework
• Hidden products: WooCommerce products hidden from the catalogue
• Your own exclusions: anything you tick "Hide from AI agents" on in the editor, or list by ID in the settings

Nothing leaves your site either. The plugin makes no calls to outside services, keeps no IP addresses, and the only data it stores is a 30-day count of connections and tool calls plus, if you turn it on, the last 100 search terms agents sent.

Every setting, explained

Everything lives under Settings, then Site MCP. The page opens with your server address, a copy button, a one-click Test the server that runs three checks as a logged-out visitor, and a readiness list that warns about plain permalinks, missing HTTPS or a site set to discourage search engines.

• Server on or off: on after activation, unless your site discourages search engines, in which case it starts off. Switched off, the server, the card and llms.txt all return 404
• What to share: tick the post types to expose (pages and posts by default) and whether to include WooCommerce products
• About your business: a one-sentence description, and an email, phone and address that agents may pass on. Leave any of them blank and it is simply not shared
• Instructions for agents: a short note every client sees on connecting, such as "quote prices in GBP" or "send people to the booking page"
• Hide by ID: a list of page, post or product IDs to keep out, for sites where editing each item is a chore
• Rate limit: requests per minute per IP address, 60 by default, anywhere from 10 to 600. Over the limit, agents get a 429 with a retry time
• Discovery files: separate switches for the server card and for llms.txt
• Search terms: off by default. On, the page shows the last 100 things agents searched for, which tells you what people ask their assistants about your business. Mention it in your privacy policy if you turn it on
• Activity: the last 30 days of connections, tool calls, which tools were used and the names of the AI clients that called, with a Clear button

In the editor, every page, post and product gets a small AI agents box with one checkbox, "Hide from AI agents". Tick it and that item disappears from every tool and from llms.txt on the next request.

Why this helps you get cited by AI assistants

This is the generative engine optimization case, and it rests on one fact: an assistant can only quote what it can read cleanly. When it scrapes a page it gets navigation, cookie banners, scripts and a layout it has to guess its way through. When it asks your MCP server, it gets your site's own description, a page as tidy Markdown, or a product with the exact current price and whether it is in stock. Clean, current, first-party facts are the easiest thing for a model to repeat correctly, and the hardest to get wrong.

The llms.txt numbers above show why a file alone is a weak signal: most of them are never read. A server that answers questions is a different kind of asset, because it is useful to any agent the moment one connects, whether it found you through a directory, the server card, or a person who added your address to their own assistant. It is the same approach we use on our own site, which is listed in the official MCP Registry, and the same thinking behind our GEO services.

What it does not change: Google's AI Overviews still work from the normal search index, so this is not a ranking signal, and an assistant that has not been pointed at your server will not know it exists. Treat Site MCP as the layer that makes you easy to use once an agent arrives, next to the basics in our guide to which AI crawlers to allow. The AI Crawler Access Checker shows in seconds whether your robots.txt is already turning them away.

Install and connect in four steps

• Install: upload the plugin zip on the Plugins screen, or install it from the WordPress.org directory once the listing is live, and activate it
• Choose: open Settings, then Site MCP, tick what to share, add a sentence about your business and save
• Test: press Test the server. If it reports a refused request, a security plugin is blocking the REST API for visitors; allow /wp-json/site-mcp/ in it
• Connect: give the address https://your-site.com/wp-json/site-mcp/v1/mcp to any MCP client, and list it in public MCP directories so agents can find it

Download: Site MCP 1.0.0 (zip, 33 KB). It is free under the GPL, version 2 or later. The plugin is on its way to the WordPress.org directory; once the listing is approved it will be linked here and updates will arrive through the normal plugin updater.

For developers

The server is a WordPress REST route that follows the MCP Streamable HTTP transport with plain JSON responses and no sessions, so it works on every host and permalink setting. It supports protocol versions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05, refuses bodies over 64 KB and batches over 10 requests, and answers GET with a 405. Nine filters let you adjust it without forking: site_mcp_post_available, site_mcp_post_markdown, site_mcp_tools, site_mcp_call_tool, site_mcp_site_info, site_mcp_server_card, site_mcp_llms_txt, site_mcp_rate_limit and site_mcp_client_ip. The last one matters behind a proxy that hides visitor addresses, where everyone would otherwise share one rate-limit bucket. If you want agents to do more than read, that is a different job with different risks; our guide to the WordPress MCP Adapter covers it.

Bottom line: Site MCP gives AI assistants a clean, read-only way to ask your WordPress site questions and get your own facts back, with nothing private exposed and nothing to pay. It is the quickest way we know to make a WordPress site easy for agents to use, and easy to quote correctly.

Frequently asked questions