Yes - Claude can connect to your own self-hosted WordPress.org site, and actually write and publish (not just read). Unlike the official WordPress.com connector, this works on any self-hosted site: install a free plugin, paste one URL, done in about two minutes. Free to start.
About two minutes, no code - the free plugin handles the app password and encryption for you.
claude mcp add --transport http. Approve once.Once connected, your AI can actually do the work across content, SEO and your store.
You stay in control. Risky changes (publish, delete, bulk edits, price changes) wait in your approval inbox - nothing goes live until you approve it. Your credentials are AES-256 encrypted and you can disconnect any time.
A technical comparison of a managed WordPress MCP server against self-hosting an open-source MCP or using WordPress.com's built-in AI.
| What you are comparing | wptaskifywhat we recommend | Raw MCP plugin | WordPress.com connector |
|---|---|---|---|
| Setup | Free plugin + paste one URL | Node.js + app password + JSON config | Official, but WP.com only |
| Approval before live | Yes - approval inbox | No | Read-only |
| Tools | 587 | ~30 | Read-only |
| WordPress + WooCommerce + Shopify | All three | WP only | WP.com only |
| Write & publish | Full write | Yes | Read-only |
| AI cost | Bring your own - no 2nd bill | Bring your own (never stated) | Same, WP.com plan required |
| Hosting | Hosted MCP, nothing to run | You self-host & maintain | First-party |
Key takeaway: self-hosted MCP setups run commands straight away and leave you holding the API keys. wptaskify runs the server, encrypts the credentials, and holds every risky action for your approval.
If your site runs a supported WordPress and PHP, it works. There is nothing to install on your own computer.
Yes. Claude can connect to a self-hosted WordPress site through wptaskify - install the free wptaskify plugin, paste one MCP URL into Claude, and your Claude can read, write, optimize and publish on your site. It works with Claude Desktop, Claude Code and claude.ai.
Create a free wptaskify account, install the free wptaskify plugin on your self-hosted WordPress.org site and click Connect (it creates and encrypts the app password for you), then copy your hosted MCP URL and add it to Claude as a custom connector. It takes about two minutes and needs no code.
No. wptaskify is bring-your-own-AI - it connects the Claude you already use (Desktop, Claude Code, or claude.ai) to your site. Your Claude does the thinking, so there is no second AI bill. wptaskify's own plans (Free, then MCP Solo, Pro, Agency) only pay for the connector and tools, never for AI tokens.
No. Manual MCP setups make you install Node.js, generate a WordPress Application Password, and edit a JSON config. wptaskify's free plugin does all of that for you - it creates the app password, encrypts it with AES-256, and gives you a hosted MCP URL to paste. No code, no terminal required (though Claude Code works too).
No. Risky changes are held in an owner approval inbox and only go live after you approve them with one click. You can revoke the connection at any time, and your credentials stay AES-256 encrypted.
Yes. wptaskify gives you one hosted MCP URL that works with Claude Desktop, Claude Code (via claude mcp add --transport http), claude.ai, and any other MCP-compatible client.
Yes. The same connector exposes store tools - Claude can create and edit WooCommerce and Shopify products, write product AEO/SEO metafields, and bulk-optimize images. WordPress + WooCommerce + Shopify all connect through one wptaskify account.
The WordPress.com connector is read-only and only works on WordPress.com paid plans - it can't publish or edit. wptaskify writes, optimizes, sells and publishes on any self-hosted WordPress site, with 587 real tools and an approval inbox before anything goes live.
You get 587 real tools, not just a text generator - content and SEO, WooCommerce/Shopify store actions, internal links, redirects, schema, sitemaps, media, menus, backups and Elementor edits.
Setup takes about two minutes. To disconnect, remove the connector in Claude or revoke the site in your wptaskify dashboard - the encrypted credentials are dropped immediately.
No fake reviews and no stock screenshots - these are live sites managed with wptaskify right now. Visit any of them yourself.
230 posts and 20 pages of product and affiliate content, written, SEO-optimized and interlinked by AI end to end.
Visit live site →Art blog recovered from zero organic - 228 posts backfilled and re-optimized by AI, sitemap and schema rebuilt.
Visit live site →French real-estate site - 623 pages of listings plus 43 posts, content and on-page SEO run on autopilot in French.
Visit live site →Tech blog - bulk meta, internal links and schema managed by AI across the catalogue.
Visit live site →AI-agency site - 57 pages of structure and home-page SEO built and maintained through wptaskify.
Visit live site →Your AI never sees this - it reads the list and picks. This is one of the 587, exactly as the server hands it over.
{
"name": "update_post_seo",
"description": "Set the SEO title, meta description and focus keyword on a post or page.",
"inputSchema": {
"type": "object",
"properties": {
"post_id": { "type": "integer", "description": "The post or page ID" },
"title": { "type": "string", "description": "SEO title" },
"description": { "type": "string", "description": "Meta description" },
"keyword": { "type": "string", "description": "Focus keyword" }
},
"required": ["post_id"]
}
}Rule-based automation and MCP solve different problems. Here is the difference, without the sales pitch.
You build the steps. When a post is published, send it here, then format it like this, then post it there. It runs exactly what you drew, every time, and it is excellent at that - moving a known thing between two known places on a schedule.
What it cannot do is decide. If the job is "find every page with a weak title and rewrite it", you have to define what weak means, in advance, as a rule.
You describe the outcome. The AI reads what is actually on your site, works out which of the 587 tools to call and in what order, and does it - then shows you anything risky before it goes live.
There is no workflow to draw and nothing to maintain when your site changes. The trade is that it is a judgement call each time rather than a fixed rule, which is why publishing waits for your approval.
They are not exclusive. Plenty of people run scheduled automations for the predictable work and use this for the parts that need reading and deciding.
You connect the Claude or ChatGPT you already pay for, so there is no second AI bill. These prices are for the server and the tools.
Indian pricing is shown in rupees on the pricing page, which has the full feature list.
wptaskify is built and run by Logical Dottech, an IT services and digital marketing agency. We use it on our own sites first - completewaterguide.com is ours, and the client sites above are ones we run. Every tool on this page exists because we needed it on real work.
Questions about how it works, or want something it does not do yet? Tell us.