Overview

AI-generated overview

A hosted MCP server that lets an assistant manage WordPress sites, WooCommerce and Shopify stores, Pinterest accounts, and Google Search Console data.

What it does: Connects an MCP client to a hosted service that performs real work on WordPress sites, Elementor layouts, WooCommerce and Shopify stores, Pinterest accounts, and Google Search Console and Analytics. Tools cover posts and pages, SEO fields, media and alt text, menus, users, themes and plugins, backups and site health, plus products, orders, refunds, discounts, boards, pins, and reporting. Risky actions such as deletes, refunds, and theme switches return an approval request and only run after a person approves them.
When to use it: Use it when you want an assistant to operate live WordPress, WooCommerce, Shopify, Pinterest, or Google Search Console accounts rather than just draft content. It suits site owners, marketers, and store operators who want changes made through chat with human approval on destructive actions.
Requirements: A remote MCP endpoint over Streamable HTTP; nothing to install or host. Authentication is OAuth 2.1 with PKCE and dynamic client registration, handled by most MCP clients on first connect; there are no static API keys. Clients that cannot do OAuth need the mcp-remote bridge. A wptaskify plan determines which tools run.

Before you install

The server can change live sites and stores: it writes content, edits themes and plugins, processes orders and refunds, and can delete data. Risky actions are gated behind an approval step that must be resolved before the call proceeds, so review each approval request. Access is granted through OAuth sign-in to your WordPress, store, Pinterest, and Google accounts, so the assistant acts with your account permissions. Some tools may involve payments or refunds.

Installation

In SourceWeft

Open wptaskify for WordPress in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wordpress": {
      "type": "http",
      "url": "https://wptaskify.com/mcp"
    }
  }
}

README

wptaskify MCP server

wptaskify is a hosted Model Context Protocol server that lets Claude, ChatGPT, Cursor or any MCP client do real work on WordPress sites, WooCommerce and Shopify stores, Pinterest accounts and Google Search Console. Risky actions (deletes, refunds, theme switches and similar) wait for a person to approve them.

Nothing to install or host: you add a URL to your AI client and sign in.

Website: https://wptaskify.com
Developer docs: https://wptaskify.com/developers
Tool reference (every tool and its parameters): https://wptaskify.com/developers/tools
Machine-readable tool list: https://wptaskify.com/developers/tools.json
Official MCP Registry: com.wptaskify/wordpress and com.wptaskify/store

This repository holds the public metadata, client configs and examples. The server itself is a hosted service.

Endpoints

Both speak MCP over Streamable HTTP (JSON-RPC 2.0).

Connect

Claude Code

Cursor (~/.cursor/mcp.json)

VS Code (.vscode/mcp.json)

Clients that only run local (stdio) servers

json

{  "mcpServers": {    "wptaskify": { "command": "npx", "args": ["-y", "mcp-remote", "https://wptaskify.com/mcp"] }  }}

{  "mcpServers": {    "wptaskify": { "command": "npx", "args": ["-y", "mcp-remote", "https://wptaskify.com/mcp"] }  }}

Claude.ai and ChatGPT connect from their own settings: see https://wptaskify.com/docs/claude and https://wptaskify.com/docs/chatgpt.

Add https://wptaskify.com/mcp/store as a second connector if you also want the store tools.

Authentication

OAuth 2.1: authorization code with PKCE (S256), public clients and dynamic client registration. Most MCP clients handle this the first time they connect.

Discovery: https://wptaskify.com/.well-known/oauth-authorization-server and https://wptaskify.com/.well-known/oauth-protected-resource
A request without a token returns 401 with WWW-Authenticate: Bearer resource_metadata=...
There are no static API keys. Use mcp-remote for clients that cannot do OAuth themselves.

What the tools cover

WordPress: posts and pages, SEO and AEO fields, schema, internal links, media and alt text, menus, users, themes and plugins, backups and site health
Elementor: read and edit page layouts
WooCommerce: products, variations, categories, coupons, orders and refunds
Shopify: products, collections, pages, articles, discounts, redirects, metafields and theme files
Pinterest: drafts, boards and sections, scheduling with safe gaps, pin and account analytics
Google: Search Console and Analytics reports

The full, current list with parameters is at https://wptaskify.com/developers/tools. Your wptaskify plan decides which tools run for you.

Approvals

A risky tool does not run straight away. It returns:

json

{  "needs_approval": true,  "approval_id": "a1b2c3",  "action": "Permanently delete post 42",  "next": "Ask the user to approve, call resolve_approval with this approval_id, then call the same tool again with the same arguments."}

{  "needs_approval": true,  "approval_id": "a1b2c3",  "action": "Permanently delete post 42",  "next": "Ask the user to approve, call resolve_approval with this approval_id, then call the same tool again with the same arguments."}

The person approves in chat or in the wptaskify dashboard; then the same call goes through.

Examples

See examples/ for raw JSON-RPC calls and sample prompts.

Links

Pricing: https://wptaskify.com/pricing
Security: https://wptaskify.com/security
Prompt library: https://wptaskify.com/prompts
WordPress plugin: https://wordpress.org/plugins/wptaskify-search-signal-for-mcp/

Built by Logical Dottech.

Source: README.md at commit 6dbb11c

Tools

0

Tool metadata has not been indexed yet.

Version history

1

v1.0.1LatestOct 6, 2026

wptaskify for WordPress