Simonov AI Site Manager turns your WordPress site into a Model Context Protocol (MCP) server: one Streamable-HTTP endpoint, served by your own site, that an AI client you connect can use to work with your content.<\/p>\n\n
Every post, page and product needs the same routine: paste the text, fix the headings, pick categories and tags, upload a picture and set it as the featured image, write an excerpt, fill in the custom fields, set the price, schedule it. Do that for everything you publish, and it adds up to hours every week.<\/p>\n\n
Connect Claude or ChatGPT, describe the result you want in plain words, and let the assistant do the clicking:<\/p>\n\n
The work that used to take a morning of copying and pasting becomes a few sentences, and it is done on your real site, in your own WordPress, with no export and no import.<\/p>\n\n
You stay in charge of what the assistant may touch. It works through a WordPress account you choose, with that account's permissions. Ask for drafts when you want to review first, switch on read-only mode when you only need answers, and check the audit log to see every change it made.<\/p>\n\n
It can manage:<\/p>\n\n
And look up, read-only:<\/p>\n\n
It does not administer the site, and it cannot be made to. There are no tools for plugins, themes, users or site settings, and every MCP request runs without administrative capabilities: managing plugins, themes, users, options or core, editing files, posting unfiltered HTML and editing theme configuration are refused for the whole request, even when the connected account is an administrator. Administration stays in the WordPress dashboard.<\/p>\n\n
Every action runs as a WordPress user you choose, so capability checks are always enforced. Read-only mode, per-tool switches, revocable connections and an audit log let you decide how much of this a client can reach.<\/p>\n\n
The plugin is the server and runs entirely on your site. There is no relay, account or service operated by the plugin author: the AI client you choose connects straight to your site's REST API, and access is granted either by you signing in to WordPress and approving the client (OAuth) or by a token you generate. Tokens are stored on your site, hashed, and can be revoked at any time from the settings page.<\/p>\n\n
WordPress 5.8 or newer and PHP 7.0 or newer. Everything works the same on old and new installs.<\/p>\n\n
Note: the configured user acts with its full WordPress capabilities. Use the least-privileged role that meets your needs, and treat the token as a site credential.<\/p>\n\n
simonov-ai-site-manager<\/code> folder to wp-content\/plugins\/<\/code> and activate it.<\/li>\n- Make sure Settings \u2192 Permalinks is set to any option other than \"Plain\".<\/li>\n
- Go to Settings \u2192 Simonov AI Site Manager, tick \"Accept MCP requests\" and save.<\/li>\n<\/ol>\n\n
The settings page shows your MCP endpoint URL<\/strong>. It is always your site address followed by \/wp-json\/wp-mcp\/v1\/mcp<\/code>:<\/p>\n\nhttps:\/\/example.com\/wp-json\/wp-mcp\/v1\/mcp\n<\/code><\/pre>\n\nPaste this full address into the client, not just the domain: the site's home page is not an MCP server.<\/p>\n\n
The client connects as the WordPress account that signs in, with that account's permissions. An Editor is enough for content work and is the safer choice.<\/p>\n\n
Connect Claude (claude.ai)<\/h4>\n\n
Custom connectors work on every Claude plan; the free plan allows one.<\/p>\n\n
\n- In claude.ai open Customize \u2192 Connectors, click \"+ Add\", then \"Add custom connector\".<\/li>\n
- Give it a name (your site's name is fine), paste the MCP endpoint URL and click \"Continue\".<\/li>\n
- Keep sign-in turned on. If Claude asks which OAuth client to use, choose \"Register automatically\". Click \"Add\".<\/li>\n
- Click \"Connect\". Claude opens your site's WordPress login in a new tab. Sign in.<\/li>\n
- The authorization screen names the address the access will be sent to. Check that it says claude.ai<\/strong>, then click \"Approve\".<\/li>\n
- In a chat, open the \"+\" menu \u2192 Connectors and switch your site on.<\/li>\n<\/ol>\n\n
Then ask, for example: \"List my five most recent drafts\" or \"Publish the post about the spring sale and set its featured image\".<\/p>\n\n
On Team and Enterprise plans an owner adds the connector once under Organization settings \u2192 Connectors; each member then clicks \"Connect\" and signs in with their own WordPress account.<\/p>\n\n
Connect ChatGPT<\/h4>\n\n
ChatGPT connects custom MCP servers through developer mode. Whether your plan offers it, and whether a workspace admin has to allow it first, is up to OpenAI \u2014 check ChatGPT's Settings \u2192 Apps.<\/p>\n\n
\n- In ChatGPT open Settings \u2192 Apps \u2192 Advanced settings and turn on developer mode.<\/li>\n
- Click \"Create app\". Give it a name, paste the MCP endpoint URL and choose OAuth as the authentication. Confirm that you trust the server and create the app.<\/li>\n
- ChatGPT opens your WordPress login. Sign in, check that the authorization screen says chatgpt.com<\/strong>, then click \"Approve\".<\/li>\n
- In a chat, open the \"+\" menu, choose developer mode and select your site.<\/li>\n<\/ol>\n\n
Tools that only read run straight away. Before anything that changes the site, ChatGPT asks you to confirm. Read what it is about to do before you confirm.<\/p>\n\n
Connect Claude Code<\/h4>\n\nclaude mcp add --transport http my-site https:\/\/example.com\/wp-json\/wp-mcp\/v1\/mcp\n<\/code><\/pre>\n\nThen run \/mcp<\/code> inside Claude Code, choose the server and authenticate. Your browser opens the same WordPress login and authorization screen.<\/p>\n\nConnect with a token (Claude Desktop config, scripts, other clients)<\/h4>\n\n
For clients that cannot sign in through a browser:<\/p>\n\n
\n- On the settings page choose \"Act as user\", then click \"Generate \/ rotate token\".<\/li>\n
- Copy the ready-made connection URL or the Claude Desktop config shown at the top of the page. The token is shown once.<\/li>\n<\/ol>\n\n
Treat the token, and any URL containing it, as a password. Generating a new token invalidates the old one.<\/p>\n\n
Use more than one client<\/h4>\n\n
Claude, ChatGPT and any other client can be connected at the same time. Each one signs in separately and appears as its own row under Active connections, where you can revoke it without affecting the others.<\/p>\n\n\n
\nHow do I connect Claude or ChatGPT?<\/h3><\/dt>\nStep-by-step instructions for claude.ai, ChatGPT, Claude Code and token-based clients are on the Installation tab. In every case you paste the MCP endpoint URL from the settings page, sign in to WordPress and approve the client.<\/p><\/dd>\n
What address do I paste into the client?<\/h3><\/dt>\nThe full MCP endpoint URL from Settings \u2192 Simonov AI Site Manager, e.g. https:\/\/example.com\/wp-json\/wp-mcp\/v1\/mcp<\/code>. Pasting only the domain does not work.<\/p><\/dd>\nThe client signs in, then says the server refused its request<\/h3><\/dt>\nAlmost always a filter in front of WordPress that blocks AI user agents, not this plugin.<\/p>\n\n
The sign-in happens in your browser, so it passes. The MCP request that follows is made by the AI provider's own servers, carrying their own user agent \u2014 and that is what gets blocked. Hence the confusing \"you signed in, but then it was refused\".<\/p>\n\n
Every provider uses separate agents for crawling and for requests a person actually asked for, and only the second kind has to be allowed:<\/p>\n\n
\n- Claude \u2014 allow
Claude-User<\/code>; ClaudeBot<\/code> and Claude-SearchBot<\/code> may stay blocked.<\/li>\n- ChatGPT \u2014 allow
ChatGPT-User<\/code>; GPTBot<\/code> and OAI-SearchBot<\/code> may stay blocked.<\/li>\n- Perplexity \u2014 allow
Perplexity-User<\/code>; PerplexityBot<\/code> may stay blocked.<\/li>\n<\/ul>\n\nAllowing the user-initiated agent does not open your site to AI training crawlers. Those arrive under the other names, and you can keep blocking every one of them.<\/p>\n\n
To check your site from any machine with curl:<\/p>\n\n
curl -A \"Claude-User\/1.0 (+Claude-User@anthropic.com)\" -o \/dev\/null -w \"%{http_code}\\n\" https:\/\/example.com\/\n<\/code><\/pre>\n\n200 means nothing is blocking. A 403, 405, 406 or 418 \u2014 especially as a plain HTML error page rather than WordPress output \u2014 means the request never reached WordPress. Run the same command without -A<\/code> to confirm the user agent is the only difference.<\/p>\n\nSuch a filter normally lives in one of three places, worth checking in this order: your hosting control panel (an option like \"Block AI bots\" or \"AI crawler protection\" \u2014 on shared hosting the rule is in the server's own nginx or Apache config, so you may have to ask support, and no plugin or .htaccess of yours can override it); Cloudflare or a similar CDN (Security \u2192 Bots \u2192 \"Block AI Scrapers and Crawlers\", or a custom WAF rule); or a security or \"AI blocker\" plugin that filters by user agent.<\/p>\n\n
Ask for the user-initiated agent to be removed from the block list by name. Blocking it is rarely deliberate \u2014 these lists are usually copied wholesale from a published crawler list, without noticing that one entry on it is how your own integrations reach the site.<\/p><\/dd>\n
How do I update the plugin?<\/h3><\/dt>\nThrough WordPress, like any other plugin from the directory: new versions appear under Dashboard \u2192 Updates and on the Plugins screen. Nothing has to be configured and nothing is fetched from anywhere but WordPress.org.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.9.2<\/h4>\n\n\n- Every tool now tells the client whether it only reads, adds something new, or can overwrite or delete. ChatGPT and other clients run reading tools without asking and ask before changes.<\/li>\n<\/ul>\n\n
0.9.1<\/h4>\n\n\n- MCP requests never hold administrative capabilities, whichever account is connected.<\/li>\n
- Removed the option, user, plugin and theme lookup tools.<\/li>\n<\/ul>\n\n
0.9.0<\/h4>\n\n\n- First release in the WordPress.org directory.<\/li>\n<\/ul>","raw_excerpt":"Free, open Model Context Protocol (MCP) server for WordPress. Lets Claude, ChatGPT and other MCP clients manage your site's content.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/390960","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=390960"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/capoeira314"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=390960"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=390960"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=390960"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=390960"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=390960"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=390960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}