WatchBase

MCP Server for structured and standardized querying of watch-related metadata such as brands, families, and reference details from WatchBase.com.

javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "watchdealer-pavel-watchbase-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/watchbase-mcp-server/build/index.js"
      ],
      "env": {
        "WATCHBASE_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can run the WatchBase MCP Server to query the WatchBase Data Feed API via MCP, enabling fast access to luxury watch metadata for inventory, research, and content creation.

How to use

You operate this server from an MCP client. The server exposes six query tools that let you search for watches, browse brands and families, and retrieve full specification details. Use the client’s MCP configuration to point to the local server and supply your API key when required. Typical workflows include locating a watch by brand or reference number, then fetching complete details for listings, comparisons, or research.

How to install

Prerequisites: install Node.js version 18 or newer, which includes Node.js 25.

Step-by-step commands to set up and run the MCP server locally:

git clone https://github.com/watchdealer-pavel/watchbase-mcp-server.git
cd watchbase-mcp-server
npm install
npm run build
npm start

Additional sections

Configuration and usage details are provided through explicit MCP client integration examples. In particular, you can run the server locally and connect via an MCP client configuration that specifies the runtime command and environment variable for authentication.

Security and access: protect your WatchBase API key. Store it in your MCP client configuration and reference it as an environment variable when starting the MCP server.

Troubleshooting tips: ensure the API key is present, verify that the server process starts without errors, and confirm that your MCP client points to the correct local command and path for index.js.

Configuration for MCP clients

To run the MCP server from a local client, you can use the following runtime configuration. This example shows a local (stdio) server started with Node.js and an API key provided through an environment variable.

{
  "mcpServers": {
    "watchbase": {
      "command": "node",
      "args": ["/path/to/watchbase-mcp-server/build/index.js"],
      "env": {
        "WATCHBASE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Notes on usage and features

The server provides six query tools for accessing the WatchBase API: search, search_refnr, list_brands, list_families, list_watches, and get_watch_details. Each tool accepts specific parameters to filter results or fetch detailed records.

Available tools

search

Query the WatchBase catalog by brand, family, watch name, or reference number; supports whole word matching.

search_refnr

Search by reference number with partial matches allowed.

list_brands

Return all watch brands present in the database.

list_families

Return all families or collections for a specified brand using brand_id.

list_watches

Fetch watches for a brand or family, with an optional date-based filter via updated_since.

get_watch_details

Retrieve full specifications for a specific watch by its id.