Buywhere MCP Server

Product search API for AI agents via Model Context Protocol. Search and compare products across Singapore and US merchants with real-time pricing, inventory, and deal discovery for AI agent commerce. Official MCP Registry. The buywhere mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

Use with Claude Desktop, Cursor, VS Code Copilot, Cline, Windsurf, OpenCode, Codex, Continue.dev, and any MCP-compatible client.

• One API — — all markets, all retailers
• Agent-native — — built for MCP from day one
• Real-time — — live pricing and availability
• Developer-first — — no SDK needed, just add the server

Adding it to your client

@buywhere/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• search_products — Search catalog by keyword, category, price, region
• get_product — Full product details by ID (prices, specs, images)
• compare_prices — Side-by-side comparison of 2–5 products
• get_price — Current prices across all merchants for one product
• get_affiliate_link — Click-tracked affiliate URL for a product
• get_catalog — Available product category taxonomy
• Windsurf — The Windsurf tool exposed by this server
• Mastra — Mastra is a TypeScript-first AI agent framework with native MCP support
• LangChain — async def main(): async with MultiServerMCPClient({ "buywhere": { "url": "https://api.buywhere.ai/mcp", "transport": "streamable_http", "headers"
• LlamaIndex — async def main(): mcp_client = BasicMCPClient( command_or_url="https://api.buywhere.ai/mcp", headers={"Authorization": f"Bearer {BUYWHERE_API_KEY}"}
• CrewAI — shopping_agent = Agent( role="Shopping Research Analyst", goal="Find the best deals across Singapore and US markets", tools=[buywhere_server], )

Configuration

You will need 2 environment variables: BUYWHERE_API_KEY, BUYWHERE_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Buywhere MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the buywhere mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Buywhere MCP's toolset — search_products, get_product, compare_prices and 8 more — is a fair guide to whether it matches your workflow. It is maintained by buywhere; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.