WatchBase MCP Server
@watchdealer-pavel
An MCP (Model Context Protocol) server providing access to the WatchBase Data Feed API for querying watch metadata.
Overview
What is WatchBase MCP Server?
An MCP (Model Context Protocol) server that provides access to the WatchBase Data Feed API for querying structured watch metadata, including brands, families, models, reference numbers, technical details, and images. It is designed for developers building applications with watch data integration.
How to use WatchBase MCP Server?
Install the server by cloning the repository, running npm install and npm run build. Configure your MCP client (e.g., VS Code extension or Claude Desktop App) to run the compiled server with a WATCHBASE_API_KEY environment variable containing your WatchBase API key. Then invoke the provided tools (like search, list_brands, get_watch_details) from your AI assistant using the use_mcp_tool command.
Key features of WatchBase MCP Server
- Search by brand, family, name, or reference number.
- Partial reference number matching via
search_refnr. - List all watch brands in the database.
- List families (collections) for a given brand ID.
- List watches with optional family and date filters.
- Retrieve full watch details by WatchBase ID.
Use cases of WatchBase MCP Server
- Look up watch specifications during authentication or appraisal.
- Build a watch collection inventory manager.
- Integrate watch metadata into a retail or e‑commerce platform.
- Answer natural language queries about watch models and references.
- Automate data enrichment for watch‑related applications.
FAQ from WatchBase MCP Server
What are the prerequisites?
Node.js and npm are required to install and run the server. You must also have a valid WatchBase API key, obtainable from the WatchBase API page.
How do I provide my API key?
Set the WATCHBASE_API_KEY environment variable in your MCP client configuration. The server reads this variable to authenticate with the WatchBase API.
What tools does this server expose?
Six tools: search, search_refnr, list_brands, list_families, list_watches, and get_watch_details. Each corresponds to a WatchBase API endpoint.
Where does the data come from?
All data is retrieved from the WatchBase Data Feed API. The server does not store or cache data locally.
What is the license?
This MCP server is licensed under the MIT License. Users should also refer to WatchBase terms of service for API usage.