BigGo

BigGo MCP Server provides access to product discovery, price history tracking, and optional specification comparisons via BigGo APIs. It supports both stdio and SSE transports, allowing flexible integration with your existing tooling. Tools available include product_search for querying products across multiple marketplaces, price_history_graph and price_history_with_history_id/with_url for visualizing and tracking price histories, and several spec-related tools (spec_indexes, spec_mapping, spec_search) to explore and query product specifications stored in Elasticsearch. Use the server to run searches, fetch price history data, and compare specs through a unified MCP interface.

Once running, you can interact with the server using the available tools to perform product searches (e.g., Look for Nike running shoes), fetch price histories by URL or history IDs, and query specification data. If you need to operate over SSE, ensure the server is configured with the correct SSE port and that clients connect to the default SSE URL (http://localhost:9876/sse) unless you override it.

Prerequisites:

• Python 3.10 or newer
• uvx package manager (included with uv)
• BigGo Certification (client_id and client_secret) for specification search

1. Obtain BigGo certification:

• Create a BigGo account if you don’t have one.
• Generate client_id and client_secret from the BigGo Certification Page.
• Save these credentials for use in the MCP server configuration (BIGGO_MCP_SERVER_CLIENT_ID and BIGGO_MCP_SERVER_CLIENT_SECRET).

2. Install and run the MCP server:

• Ensure Python is installed and accessible in your PATH.
• Use uvx to install/run the BigGo MCP Server as described in the Installation Config.

3. Configure environment variables:

• Set BIGGO_MCP_SERVER_CLIENT_ID to your BigGo client_id.
• Set BIGGO_MCP_SERVER_CLIENT_SECRET to your BigGo client_secret.
• Optionally set BIGGO_MCP_SERVER_REGION to your desired search region (default is TW).

4. Start the server using the provided configuration. Example:

{
  "mcpServers": {
    "biggo-mcp-server": {
      "command": "uvx",
      "args": ["BigGo-MCP-Server@latest"],
      "env": {
        "BIGGO_MCP_SERVER_CLIENT_ID": "YOUR_CLIENT_ID",
        "BIGGO_MCP_SERVER_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "BIGGO_MCP_SERVER_REGION": "US"
      }
    }
  }
}

5. Verify the server is running by attempting a sample tool call or by checking the SSE endpoint if used.

Notes and tips:

• The server relies on BigGo credentials for specification-related searches; without valid credentials, spec-related tools will not be able to query Elasticsearch.
• The SSE transport requires the BIGGO_MCP_SERVER_SSE_PORT to be open and accessible; if you change the port, ensure clients point to the new URL.
• If you need a specific version, you can use BigGo-MCP-Server@VERSION in the args (e.g., BigGo-MCP-Server@0.1.1).
• The Available Tools section lists commands you can call to perform tasks such as product_search, price_history_graph, price_history_with_history_id, price_history_with_url, spec_indexes, spec_mapping, spec_search, and get_current_region.
• Environment variables are required for specification search; ensure they are not exposed publicly in insecure environments.