BigGo MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is BigGo MCP Server?

BigGo MCP Server is a tool that utilizes APIs from BigGo, a professional price comparison website, to help users discover products and track their prices across various e-commerce platforms.

How to use BigGo MCP Server?

To use the BigGo MCP Server, install it using the uvx package manager, configure it with your BigGo certification credentials, and then utilize its tools for product discovery and price tracking.

Key features of BigGo MCP Server?

  • Product Discovery: Search for products across multiple e-commerce platforms like Amazon, Aliexpress, and more.
  • Price History Tracking: Track the price history of products by providing their URLs or related terms.
  • Specification Comparison: Compare products based on their specifications (Note: This feature is disabled in versions >= v0.1.28).

Use cases of BigGo MCP Server?

  1. Finding the best prices for electronics across different online stores.
  2. Monitoring price changes for specific products over time.
  3. Comparing specifications of various products to make informed purchasing decisions.

FAQ from BigGo MCP Server?

  • How do I obtain BigGo certification?

Register for a BigGo account and generate your client ID and client secret from the BigGo Certification Page.

  • What are the prerequisites for installation?

You need Python >= 3.10 and the uvx package manager.

  • Can I track prices for any product?

Yes, as long as you provide the correct product URL or related terms.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago