Skip to main content
Glama
WatchBase MCP Server

WatchBase MCP Server

WatchBase MCP Server

Node.js 18+ License: MIT

An MCP (Model Context Protocol) server providing access to the WatchBase Data Feed API for querying comprehensive watch metadata.

What is WatchBase?

WatchBase is a comprehensive watch database containing detailed information about luxury watches, including:

  • 280+ brands (Rolex, Patek Philippe, Audemars Piguet, etc.)

  • Thousands of watch families/collections

  • Technical specifications (case size, movement, complications, etc.)

  • Reference numbers for precise identification

Related MCP server: mcp-mediawiki-crunchtools

Features

This MCP server provides 6 tools for querying the WatchBase API:

Tool

Description

Required Params

search

Search by brand, family, watch name, or reference number (whole words)

q

search_refnr

Search by reference number (partial matches allowed)

q

list_brands

Get all watch brands in the database

—

list_families

Get all families/collections for a brand

brand_id

list_watches

Get watches for a brand/family (with optional date filter)

brand_id

get_watch_details

Get full specifications for a specific watch

id

Prerequisites

Quick Start

1. Clone and Install

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

2. Configure Your MCP Client

Add to your MCP client configuration:

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

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

Claude Code (.mcp.json in your project):

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

3. Restart Your MCP Client

Restart Claude Desktop or Claude Code to load the new MCP server.

Usage Examples

Search for a Watch

Search for "Royal Oak" watches
→ Uses: search tool with q="Royal Oak"

Search by Reference Number

Find watches with reference number starting with "15500"
→ Uses: search_refnr tool with q="15500"

Browse Brands and Families

List all Rolex families
→ Uses: list_brands to find Rolex ID, then list_families with brand_id

Get Watch Specifications

Get full details for watch ID 12345
→ Uses: get_watch_details tool with id=12345

API Response Examples

Brand Object

{
  "id": 59,
  "name": "Audemars Piguet"
}

Watch List Response

{
  "id": 11702,
  "refnr": "15500ST.OO.1220ST.01",
  "name": "Royal Oak",
  "brand": { "id": 59, "name": "Audemars Piguet" },
  "family": { "id": 234, "name": "Royal Oak" },
  "thumb": "https://cdn.watchbase.com/watch/medium/...",
  "updated": "2024-01-15"
}

Watch Details Response

Includes all fields plus:

  • caliber — Movement details

  • case — Case specifications

  • dial — Dial information

  • added, modified, published — Metadata dates

For Watch Dealers

This MCP server is perfect for:

  1. Inventory Management — Look up reference numbers and specifications

  2. Price Research — Get detailed specs to compare with market prices

  3. Authentication — Verify reference numbers and specifications

  4. Content Creation — Generate accurate watch descriptions

  5. Customer Service — Quickly answer questions about any watch

Typical Workflow

  1. Search by reference number — search_refnr with partial ref

  2. Get watch ID from search results

  3. Fetch full details — get_watch_details with ID

  4. Use specifications for listings, comparisons, or research

Incremental Sync for Large Inventories

Use list_watches with updated_since parameter to sync only changed records:

list_watches with brand_id=59, updated_since="2024-01-01"
→ Returns only watches updated after Jan 1, 2024

API Documentation

See watchbase_api_reference.md for detailed API documentation.

Development

# Watch mode (auto-rebuild on changes)
npm run dev

# Manual build
npm run build

# Run the server directly
npm start

Troubleshooting

"WATCHBASE_API_KEY environment variable is required"

Make sure you've added the WATCHBASE_API_KEY to your MCP client's env configuration.

"WatchBase API error: Invalid or unauthorized API key"

Your API key may be invalid or expired. Contact WatchBase support.

Server not appearing in Claude

  1. Check the path to build/index.js is correct

  2. Restart Claude Desktop/Code

  3. Check logs for connection errors

License

MIT License — see LICENSE file.

Note: This MCP server is an independent project. Please refer to WatchBase Terms of Service for API usage policies.

Available Tools

6 tools
get_watch_detailsC

Retrieve the full details for a particular watch by its ID.

Inputs: id (required).

list_brandsB

Retrieve a list of all brands in the database.

Inputs: no named parameters.

list_familiesC

Retrieve a list of all families for a given brand.

Inputs: brand_id (required).

list_watchesC

Retrieve a list of watches for a particular Brand and/or Family, optionally filtered by update date.

Inputs: brand_id (required), family_id, updated_since.

search_refnrB

Search the database by reference number (allows partial matches).

Inputs: q (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools have distinct purposes, but 'search' and 'search_refnr' create ambiguity as both handle reference number searches, with overlapping functionality that could cause misselection. The other tools (get_watch_details, list_brands, list_families, list_watches) are clearly differentiated by their specific resource and action.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_watch_details, list_brands, search_refnr). There are no deviations in naming conventions, making the set predictable and readable for an agent.

    Tool Count5/5

    With 6 tools, this server is well-scoped for its watch database domain. Each tool serves a clear purpose, such as retrieving details, listing categories, or searching, without being overly sparse or bloated, fitting typical expectations for a focused MCP server.

    Completeness4/5

    The tool set covers core read operations for watches, brands, and families, including search capabilities, which is appropriate for a database query server. A minor gap exists in the lack of write operations (e.g., create, update, delete), but this may be intentional for a read-only interface, and agents can still perform comprehensive queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP Server for accessing W3C/WHATWG/IETF web specifications. Provides AI assistants with access to official web standards data including specifications, WebIDL definitions, CSS properties, and HTML elements.
      11
      16 npm
      4
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A secure MCP server for interacting with MediaWiki instances, allowing users to search, read, create, and manage wiki content like pages, categories, and files. It supports both public and private wikis with comprehensive authentication for full read and write operations.
      19
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server designed for interacting with the Model Context Protocol Registry API to discover and retrieve information about available MCP servers. It provides tools to search, list, and view detailed configurations and version history for servers within the registry.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A versatile MCP server that connects to multiple relational databases (MySQL, PostgreSQL, Oracle, SQL Server, SQLite) and enables secure read-only SQL query execution and metadata access.
      4
      -