WordPress MCP vs Wptaskify for stores
A side-by-side look at the WordPress MCP and Wptaskify for stores MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose WordPress MCP for e-commerce work over a hosted endpoint; choose Wptaskify for stores for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose WordPress MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
Choose Wptaskify for stores when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 40/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View WordPress MCP | View Wptaskify for stores |
Tools & capabilities
WordPress MCP tools
No tool names declared yet. Check the project README from the listing page.
Wptaskify for stores tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WordPress MCP
{
"mcpServers": {
"wordpress-mcp-2": {
"url": "https://client.example.com/wp-json/wp-mcp/v1/mcp"
}
}
}
Wptaskify for stores
{
"mcpServers": {
"wptaskify-for-stores": {
"url": "https://wptaskify.com/mcp"
}
}
}
Frequently asked questions
WordPress MCP is categorized under E-Commerce and uses a remote HTTP/SSE transport. Wptaskify for stores belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick WordPress MCP for e-commerce work and Wptaskify for stores for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
WordPress MCP has no declared pricing — check the project's own site. Wptaskify for stores has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wordpress-mcp-2 and wptaskify-for-stores as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WordPress MCP has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Wptaskify for stores has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.