The WatchBase MCP Server provides access to the WatchBase Data Feed API, allowing you to query a comprehensive database of watch metadata including brands, collections, reference numbers, technical details, and images.
Clone the repository:
git clone https://github.com/watchdealer-pavel/watchbase-mcp.git
cd watchbase-mcp
Install dependencies:
npm install
Build the server:
npm run build
You must provide your WatchBase API key via the WATCHBASE_API_KEY
environment variable. Configure your MCP client (like Cline/Roo Code or Claude Desktop App) with this key.
Open your VS Code settings for MCP servers (typically at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
)
Add the following configuration:
"watchbase-mcp": {
"command": "node",
"args": ["/path/to/your/watchbase-mcp/build/index.js"],
"env": {
"WATCHBASE_API_KEY": "YOUR_WATCHBASE_API_KEY"
},
"disabled": false,
"autoApprove": []
}
Open the Claude Desktop App configuration file (typically at ~/Library/Application Support/Claude/claude_desktop_config.json
)
Add the following configuration:
"watchbase-mcp": {
"command": "node",
"args": ["/path/to/your/watchbase-mcp/build/index.js"],
"env": {
"WATCHBASE_API_KEY": "YOUR_WATCHBASE_API_KEY"
},
"disabled": false,
"autoApprove": []
}
The server provides six tools corresponding to WatchBase API endpoints.
Search the database by brand name, family name, watch name, and reference number:
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>search</tool_name>
<arguments>
{
"q": "priors court"
}
</arguments>
</use_mcp_tool>
Search the database by reference number (allows partial matches):
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>search_refnr</tool_name>
<arguments>
{
"q": "P2/"
}
</arguments>
</use_mcp_tool>
Retrieve a list of all watch brands in the database:
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>list_brands</tool_name>
<arguments>
{}
</arguments>
</use_mcp_tool>
Retrieve all families (collections) for a given brand ID:
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>list_families</tool_name>
<arguments>
{
"brand_id": 37
}
</arguments>
</use_mcp_tool>
Retrieve watches for a particular brand and optional family:
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>list_watches</tool_name>
<arguments>
{
"brand_id": 37,
"family_id": 279
}
</arguments>
</use_mcp_tool>
Retrieve full details for a specific watch by its WatchBase ID:
<use_mcp_tool>
<server_name>watchbase-mcp</server_name>
<tool_name>get_watch_details</tool_name>
<arguments>
{
"id": 17289
}
</arguments>
</use_mcp_tool>
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.