Markifact: AI Performance Marketing vs Wptaskify for stores
A side-by-side look at the Markifact: AI Performance Marketing 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.
W
Wptaskify for storesFinance & Fintech · Remote HTTP/SSELet your AI manage WooCommerce and Shopify stores: products, SEO, descriptions and images.40FairAuth: not declaredVerdict: choose Markifact: AI Performance Marketing for finance & fintech work over a hosted endpoint; choose Wptaskify for stores for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Markifact: AI Performance Marketing when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
WChoose Wptaskify for stores when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wptaskify for stores | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 44/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 | 51 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Markifact: AI Performance Marketing | View Wptaskify for stores |
Tools & capabilities
Markifact: AI Performance Marketing 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.
Markifact: AI Performance Marketing
{
"mcpServers": {
"markifact-ai-performance-marketing": {
"url": "https://api.markifact.com/mcp"
}
}
}
Wptaskify for stores
{
"mcpServers": {
"wptaskify-for-stores": {
"url": "https://wptaskify.com/mcp"
}
}
}
Frequently asked questions
Markifact: AI Performance Marketing is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Wptaskify for stores belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Markifact: AI Performance Marketing for finance & fintech work and Wptaskify for stores for finance & fintech.
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.
Markifact: AI Performance Marketing 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 markifact-ai-performance-marketing and wptaskify-for-stores as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markifact: AI Performance Marketing has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 51 GitHub stars. Wptaskify for stores has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.