Side-by-Side Model Context Protocol Comparison
Store Builder vs Wpagent MCP
In-depth architectural comparison of the Store Builder and Wpagent MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Store Builder
E-Commerce · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Wpagent MCP
E-Commerce · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Store Builder if you need specialized E-Commerce tools running via a local process. Choose Wpagent MCP if your workspace requires E-Commerce integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Store Builder when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
SB_API, SB_TOKEN, SB_SITE, SB_SITE_NAME, SB_EMAIL, SB_PASSWORD, PEXELS_API_KEYS. - Primary tools included: sb_connect, sb_site_list, sb_api_find.
Choose Wpagent MCP when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
WP_SITE_URL, WP_API_KEY_ID, WP_API_SECRET. - Primary tools included: WordPress content and custom post type management, Plugin and theme installation and lifecycle controls, WooCommerce orders, settings, coupons, and tax tools.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Store Builder Tools (37)
sb_connect
Log in, list the sites this account can operate, report which credentials are present
sb_site_list
List the sites this account can operate
sb_api_find
Find API operations by intent — one line per match — then read one operation's call sheet by id: real parameter schemas, the credential it needs, and the body's fields read off the handler that decodes them, each carrying the trap its own doc comment records
sb_api_call
Execute an operation, or any route by method+path; dry run by default. Field selection and local result pagination; `merge` for whole-record PUTs, `If-Match`, multipart `file
sb_page_open
Open a page for editing and return its outline — or, with `form_id`, a form's field document (fields, defaults, dependent-field rules)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Store Builder Configuration
Wpagent MCP Configuration