Swipefast vs Wpagent MCP
A side-by-side look at the Swipefast and Wpagent MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SwipefastE-CommerceThe checkout your AI builds: checkouts, order bumps and upsells, with live changes you approve.36FairAuth: api key requiredVerdict: choose Swipefast for e-commerce work; choose Wpagent MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Swipefast when
- You need dedicated capabilities in the E-Commerce domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
SWIPEFAST_API_KEY.
Choose Wpagent MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WP_SITE_URL, WP_API_KEY_ID, WP_API_SECRET.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Swipefast | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 36/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | SWIPEFAST_API_KEY | WP_SITE_URLWP_API_KEY_IDWP_API_SECRET |
Tools & capabilities
Swipefast tools
No tool names declared yet. Check the project README from the listing page.
Wpagent MCP 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.
Swipefast
No confirmed install command for Swipefast yet — follow the setup steps linked from its listing page rather than a guessed package name.
Wpagent MCP
{
"mcpServers": {
"wpagent-mcp": {
"command": "npx",
"args": [
"-y",
"wpagent-mcp"
],
"env": {
"WP_SITE_URL": "YOUR_WP_SITE_URL_HERE",
"WP_API_KEY_ID": "YOUR_WP_API_KEY_ID_HERE",
"WP_API_SECRET": "YOUR_WP_API_SECRET_HERE"
}
}
}
}
Frequently asked questions
Swipefast is categorized under E-Commerce and uses an install path we have not confirmed yet. Wpagent MCP belongs to E-Commerce and uses a local stdio subprocess. Pick Swipefast for e-commerce work and Wpagent MCP 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. Swipefast has no confirmed install command yet — follow its own setup instructions.
Swipefast is listed as a paid service. Auth: api key required. Wpagent MCP 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 swipefast and wpagent-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Swipefast has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Wpagent MCP has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
