Skip to content

Add BuyWhere buywhere-api MCP server#1356

Open
BuyWhere wants to merge 3 commits into
modelcontextprotocol:mainfrom
BuyWhere:add-buywhere-buywhere-api-server
Open

Add BuyWhere buywhere-api MCP server#1356
BuyWhere wants to merge 3 commits into
modelcontextprotocol:mainfrom
BuyWhere:add-buywhere-buywhere-api-server

Conversation

@BuyWhere

Copy link
Copy Markdown

BuyWhere MCP Server Registration

Namespace: io.github.BuyWhere/buywhere-api
MCP Server Name: buywhere-catalog
Version: 0.1.0
Transport: HTTP (JSON-RPC 2.0 over HTTP POST)
Endpoint: mcp.buywhere.io

Tools

  • search_products - Full-text product search across merchants
  • get_product - Product details by ID
  • compare_products - Cross-merchant price comparison
  • get_deals - Active deals and discounts
  • list_categories - Browse product categories
  • find_best_price - Find lowest price for a product
  • ingest_products - Bulk product ingestion

Description

BuyWhere product catalog MCP server - search, compare, and ingest product data across merchants via natural language. Connects to PostgreSQL with full-text search.

Repository

https://github.com/BuyWhere/buywhere


This PR was created automatically by the BuyWhere fleet agent.
Co-Authored-By: Paperclip noreply@paperclip.ing

BuyWhere and others added 2 commits June 12, 2026 02:43
Namespace: io.github.BuyWhere
MCP server: buywhere-catalog
Version: 0.1.0
Transport: HTTP (JSON-RPC 2.0)
Tools: search_products, get_product, compare_products, get_deals, list_categories, find_best_price, ingest_products

Co-Authored-By: Paperclip <noreply@paperclip.ing>

@BuyWhere BuyWhere left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR still open — continuing to poll per BUY-42685.

@BuyWhere

Copy link
Copy Markdown
Author

Following up on this PR (12+ hours since submission, awaiting maintainer review).

Quick status note for reviewers: The PR currently uses:

  • mcp.buywhere.io (deprecated, NXDOMAIN)
  • io.github.BuyWhere/buywhere-api namespace
  • Version 0.1.0

The canonical configuration (live today) is:

  • https://api.buywhere.ai/mcp (canonical endpoint)
  • io.github.BuyWhere/buywhere-mcp (matching npm package @buywhere/mcp-server)
  • Latest version 1.0.4 (with the auth header fix from BuyWhere/buywhere-mcp#4603226)

Recommended path forward (faster than re-reviewing this PR):

  • Close this PR as superseded
  • Open a new PR with the corrected server config (api.buywhere.ai/mcp endpoint, buywhere-mcp namespace, v1.0.4)
  • Reference BuyWhere/buywhere-mcp issue #18 for the auth fix context

If maintainers prefer the iterative-update path (commits on this PR), I'm happy to do that too. Just let me know which approach is faster.

Reference data: https://registry.modelcontextprotocol.io/v0/servers?search=buywhere (current v1.0.4 row)

@BuyWhere

Copy link
Copy Markdown
Author

Update (2026-06-12): Pushed a fix to shorten the description (was 163 chars, now <100).

Also opened a complementary PR #1357 with the correct namespace io.github.BuyWhere/buywhere-mcp (matching the canonical npm package @buywhere/mcp-server) and the latest version 1.0.4 (with the auth header fix from BUY-42672).

Recommendation for maintainer: Close this PR (#1356) and merge #1357 instead. The #1357 entry:

  • Uses the correct namespace (buywhere-mcp not buywhere-api)
  • Uses the correct endpoint (https://api.buywhere.ai/mcp not mcp.buywhere.io)
  • Uses the latest version 1.0.4 (not 0.1.0)
  • Has a description that passes the 100-char schema validation

/tmp/mcp-publisher validate passes on the new file. The BuyWhere/registry fork is in sync with the modelcontextprotocol/registry for both branches.

@BuyWhere

Copy link
Copy Markdown
Author

@maintainer friendly bump — this PR is part of BuyWherer's June 30 directory target. Any tweaks needed to land?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant