BuyWhere MCP Server vs Jewelry by Sweet Pea Products
A side-by-side look at the BuyWhere MCP Server and Jewelry by Sweet Pea Products MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
J
Jewelry by Sweet Pea ProductsE-CommerceLive search of 100,000+ fine jewelry products, prices and store policies. Read-only, no auth.37FairAuth: not declaredVerdict: choose BuyWhere MCP Server for e-commerce work over a hosted endpoint; choose Jewelry by Sweet Pea Products for e-commerce. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BuyWhere MCP Server when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
BUYWHERE_API_KEY, BUYWHERE_API_URL.
JChoose Jewelry by Sweet Pea Products when
- You need dedicated capabilities in the E-Commerce domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | J Jewelry by Sweet Pea Products | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 37/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | BUYWHERE_API_KEYBUYWHERE_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View BuyWhere MCP Server | View Jewelry by Sweet Pea Products |
Tools & capabilities
BuyWhere MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Jewelry by Sweet Pea Products 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.
BuyWhere MCP Server
{
"mcpServers": {
"buywhere-mcp-server": {
"url": "https://api.buywhere.ai"
}
}
}
Jewelry by Sweet Pea Products
No confirmed install command for Jewelry by Sweet Pea Products yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
BuyWhere MCP Server is categorized under E-Commerce and uses a remote HTTP/SSE transport. Jewelry by Sweet Pea Products belongs to E-Commerce and uses an install path we have not confirmed yet. Pick BuyWhere MCP Server for e-commerce work and Jewelry by Sweet Pea Products 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. Jewelry by Sweet Pea Products has no confirmed install command yet — follow its own setup instructions.
BuyWhere MCP Server has no declared pricing — check the project's own site. Jewelry by Sweet Pea Products 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 buywhere-mcp-server and jewelry-by-sweet-pea-products as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BuyWhere MCP Server has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 2 GitHub stars. Jewelry by Sweet Pea Products has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.