Wptaskify for stores

What wptaskify for stores MCP server does

The wptaskify for stores MCP server exposes store-management tools for WooCommerce and Shopify through the Model Context Protocol. It is a hosted service rather than a package that you run locally. AI clients connect to the store-specific endpoint, authenticate with wptaskify, and then call tools against the stores you authorize.

The available scope depends on the connected platform and your wptaskify plan. The README identifies WooCommerce support for products, variations, categories, coupons, orders, and refunds. Shopify coverage includes products, collections, pages, articles, discounts, redirects, metafields, and theme files.

How it works

Connect an MCP-compatible client to https://wptaskify.com/mcp/store using Streamable HTTP and JSON-RPC 2.0. On the first connection, the service uses OAuth 2.1 with authorization code flow and PKCE. Public clients and dynamic client registration are supported, and there are no static API keys.

A tool that could make a consequential change may return an approval request instead of executing immediately. The response includes an approval ID and instructions to obtain user confirmation, resolve the approval, and repeat the original call with the same arguments. Approval can happen in the chat interface or in the wptaskify dashboard.

Setup and configuration

Add the store endpoint as an HTTP MCP server in a client that supports remote MCP connections. Cursor and VS Code examples in the repository use the endpoint directly. Claude Code can add it with an HTTP transport command. Clients that only support local stdio servers can use mcp-remote through npx as a bridge.

If you also need WordPress, Pinterest, Google Search Console, or Google Analytics tools, configure the separate https://wptaskify.com/mcp endpoint. The /mcp/store endpoint is the one intended for WooCommerce and Shopify tools.

Tools and capabilities

The store tool set can support tasks such as:

• Reviewing and updating WooCommerce products, variations, categories, coupons, orders, and refunds.
• Managing Shopify products, collections, pages, articles, discounts, redirects, metafields, and theme files.
• Having an agent work with catalog and store-content data from an approved AI client.
• Requiring a person to confirm risky actions before the service completes them.

The current tool names and parameters are maintained in wptaskify’s online tool reference and machine-readable tool list. Check those resources before building prompts or automation that depends on a particular operation.

Limitations and notes

wptaskify for stores MCP server is hosted, so this repository contains metadata, client configurations, and examples rather than the server implementation. You need a wptaskify account or plan that includes the tools you intend to call; the README states that the plan determines which tools run.

Clients without native OAuth support cannot use a static API key because none is provided. Use mcp-remote for those clients. The service may also require approval for deletes, refunds, theme switches, and similar risky operations, so unattended workflows should account for an approval step. Consult the live documentation for the exact tool inventory and parameters.