Site Answers – MCP Server, llms.txt & AI Crawler Log
AI assistants are reading your website. Site Answers has one job: make your site readable to them, show you whether they actually came, let you decide which of them may, and let the AI agents you choose search and read it directly. These parts make a WordPress site agent-ready, and together they are
AI assistants are reading your website. Site Answers has one job: make your site readable to them, show you whether they actually came, let you decide which of them may, and let the AI agents you choose search and read it directly. These parts make a WordPress site agent-ready, and together they are the whole plugin.
It is a read-only MCP server for AI agents. MCP, the Model Context Protocol, is the standard way AI assistants such as Claude, ChatGPT and Cursor connect to tools. Make a token under Site Answers → AI Agents (MCP) , give your agent the address and the token, and it can search your published posts and pages and read any of them as clean Markdown. It gets four tools: search_content , get_post , list_recent and get_site_info . It cannot change anything: there are no write tools at all, not even switched-off ones. Each token is revocable and limited to 60 calls a minute, and the access log shows which token used which tool on which page, and when. If your site runs WordPress’s official MCP Adapter plugin, the same four tools are registered as WordPress abilities too, so its agents get them with no token at all.
It publishes an llms.txt file. llms.txt is an emerging convention — a plain, readable Markdown index at the root of your site that tells AI assistants what you have published and where to find it. Site Answers builds yours from your own posts and pages: your site name, your tagline, then one line per URL with its title and a short description. It is rebuilt automatically whenever you publish, edit or delete something, so it never goes stale.
It publishes llms-full.txt too. Where llms.txt is the map, llms-full.txt is the whole territory: the full text of every page llms.txt lists, one after another, in one file, so an AI assistant can read your site in a single visit. Same pages, same exclusions, capped at 5 MB with a note saying where the rest is. You can switch it off in Settings.
It logs which AI crawlers visit. GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, CCBot and the others are recognised by name. For each visit you see which crawler came, which page it asked for, and whether it got the page or an error. That answers a plain question: is AI search actually reading my content, and which pages does it want?
It serves a clean Markdown copy of every page. Add .md to the end of any post or page address and you get the article as plain Markdown — headings, paragraphs, lists, links and tables — with the navigation, sidebars, share buttons and scripts left out. That is what an automated reader wants, and it is far less likely to be misquoted than a page it had to dig out of a theme. Each HTML page also advertises its Markdown twin in a Link header, so a crawler can find it without guessing.