BuyWhere MCP Server
Real-time product search and price comparison across 11M+ products from Singapore, Southeast Asia, and US marketplaces via a remote streamable-HTTP MCP endpoint with API key auth.
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Canonical URL
- https://heyclau.de/entry/mcp/buywhere-mcp-server
- Source URLs
- https://github.com/BuyWhere/buywhere-mcp/blob/main/README.md, https://github.com/BuyWhere/buywhere-mcp, https://buywhere.ai
- Brand
- BuyWhere
- Brand domain
- buywhere.ai
- Brand asset source
- brandfetch
- Safety notes
- Read-only product catalog access by default; no write or delete operations exposed., API key should be stored in the MCP client config or environment, never committed.
- Privacy notes
- BuyWhere API key is sent as a Bearer token in the Authorization header on every request., Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses., BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing.
- Author
- BuyWhere
- Submitted by
- BuyWhere
- Claim status
- unclaimed
- Last verified
- 2026-06-26
Safety notes
- Read-only product catalog access by default; no write or delete operations exposed.
- API key should be stored in the MCP client config or environment, never committed.
Privacy notes
- BuyWhere API key is sent as a Bearer token in the Authorization header on every request.
- Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses.
- BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing.
Prerequisites
- A BuyWhere API key (free at https://buywhere.ai/api-keys).
- An MCP client such as Claude Code, Claude Desktop, Cursor, Windsurf, or any MCP-compatible host.
- Network access to https://api.buywhere.ai.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://buywhere.ai
Full copyable content
{
"mcpServers": {
"buywhere": {
"type": "http",
"url": "https://api.buywhere.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_BUYWHERE_API_KEY"
}
}
}
}About this resource
What it does
The BuyWhere MCP server exposes a real-time cross-border e-commerce catalog to Claude via the Model Context Protocol. It returns live product listings, prices, and deals from marketplaces across Singapore, Southeast Asia, and the United States.
- Search products — query by keyword, category, merchant, or market
- Compare prices — see the same product across multiple merchants in one response
- Retrieve deals — fetch current promotional pricing
- List categories — browse the supported taxonomy
How it works
BuyWhere's MCP endpoint is a remote streamable-http server hosted at https://api.buywhere.ai/mcp.
Authentication uses a bearer-token API key. There is no local install — connect your MCP client to
the hosted endpoint and the catalog is immediately available.
License
MIT licensed. Free API key available at https://buywhere.ai/api-keys.
Source citations
Add this badge to your README
How it compares
BuyWhere MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Real-time product search and price comparison across 11M+ products from Singapore, Southeast Asia, and US marketplaces via a remote streamable-HTTP MCP endpoint with API key auth. Open dossier | Local-first codebase intelligence MCP server that indexes repositories with tree-sitter, stores searchable chunks in DuckDB, and gives Claude semantic search, regex search, daemon status, and deep code research tools. Open dossier | Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases. Open dossier | MCP server for Google Search Console that lets Claude list properties, inspect indexing status, query search analytics, compare performance periods, audit sitemaps, and manage Search Console resources with guarded destructive tools. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | BuyWhere | ChunkHound | johnhuang316 | Amin Foroutan |
| Added | 2026-06-26 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | Claude CodeCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Read-only product catalog access by default; no write or delete operations exposed. API key should be stored in the MCP client config or environment, never committed. | ✓ChunkHound reads source files, Markdown, text, PDFs, and supported config files under the target directory and stores indexed chunks in a local database. Realtime indexing and daemon mode can continue watching project files after the initial MCP connection. Code research and web search tools require embedding, reranking, and LLM configuration and may invoke local CLIs or external model APIs depending on settings. Exclude generated files, vendored dependencies, secrets, large artifacts, and unrelated repositories before indexing broad workspace roots. Review MCP client configuration carefully when using an absolute project path in a global Claude Desktop config. | ✓Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources. Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths. Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases. The server can create and clear index/cache settings and temporary directories used for stored index data. Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository. | ✓The server requests the Google Search Console webmasters scope and can access every property available to the authenticated account. add_site, delete_site, and delete_sitemap are disabled by default and only run when GSC_ALLOW_DESTRUCTIVE is true. manage_sitemaps can submit or delete sitemaps depending on action and destructive settings. URL inspection and analytics tools can reveal indexing issues, search terms, landing pages, countries, devices, click-through rates, and ranking positions. Use least-privilege service accounts, avoid full-access credentials where read-only analysis is enough, and confirm exact site_url values with list_properties. |
| Privacy notes | ✓BuyWhere API key is sent as a Bearer token in the Authorization header on every request. Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses. BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing. | ✓Indexed chunks, file paths, symbols, comments, Markdown, PDFs, configuration values, database files, daemon state, and search results can reveal proprietary source code and internal architecture. Embedding, reranking, LLM, and web search providers may receive code-derived queries or snippets if configured. Local ChunkHound database files, logs, daemon state, and MCP transcripts may retain code-derived context after the session ends. Avoid sharing ChunkHound databases, config files with API keys, verbose logs, research outputs, and screenshots from private repositories. | ✓Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings. Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree. File watcher status, exclude patterns, and settings can reveal local project layout and development conventions. If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine. Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing. | ✓OAuth client secrets, service account JSON, cached token files, Search Console properties, page URLs, query terms, sitemap URLs, countries, devices, clicks, impressions, CTR, and positions can be sensitive. The server stores OAuth tokens under a user config directory unless GSC_CONFIG_DIR is changed. Service account files and OAuth tokens must stay out of prompts, issue comments, logs, screenshots, and repository files. Redact property URLs, query data, page URLs, tokens, credential file paths, and inspection results before sharing MCP transcripts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.