# Harris Boat Works - Mercury Repower

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/harrisboatworks/mercury-builder-pro  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/harris-boat-works-mercury-repower

## Description
Live Mercury outboard data and CAD quote builder from a Mercury Platinum Dealer in Ontario.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Harris Boat Works - Mercury Repower does

Harris Boat Works - Mercury Repower is the public Mercury outboard catalogue and quote-building application for Harris Boat Works. The repository is maintained on GitHub, with the `main` branch treated as the authoritative source and Vercel used for production releases.

The material also describes inventory synchronization from Lightspeed DMS through the `mercury_motor_inventory` view. That synchronization is separate from the public quote-building experience: the public application must not call `sync-lightspeed-inventory`.

## How it works

Local development uses Node.js on the 22 line, version 22.22.2 or newer. The application runs with Vite on port 8080. Production deployment follows the Harris Boat Works Vercel project, and merges or production deployments require explicit authorization.

Repository checks distinguish between routine frontend validation and server-side or release-adjacent work. Small frontend changes use `npm run verify:small`. API and Supabase Edge Function changes require their scoped type checks. The full build performs content generation, live Google Places retrieval, and an IndexNow request, so it is treated as release-adjacent external work rather than a routine check.

## Setup and configuration

For Harris Boat Works - Mercury Repower, use the following local setup:

```sh
npm ci --ignore-scripts
npm run dev
```

The development server is available at `http://localhost:8080`. The tracked `.env` file is intended for public values only. Private local overrides belong in `.env.local`, while deployment secrets should remain in Vercel or Supabase secret storage. The repository explicitly prohibits placing secrets in source files, shell history, documentation, logs, commits, or model-worker prompts.

Generated files should be changed through their owning source or generator rather than edited directly. After relevant changes, run the named generation or validation script and review the resulting diff.

## Tools and capabilities

The documented application capabilities include:

- Browsing Mercury outboard catalogue data.
- Building quotes from the available Mercury product information.
- Using inventory sourced from the Lightspeed DMS view.
- Running a local Vite development server for application work.
- Validating frontend, Vite configuration, API, and Edge Function changes with repository scripts.

It therefore supports describing the catalogue and quote-builder functions, but not specific agent-callable operations beyond those application functions.

## Limitations and notes

The public quote builder must not trigger inventory synchronization. Manual inventory synchronization belongs in the authenticated admin Stock Sync or inventory dashboard, and nightly synchronization is described as a server-side scheduler responsibility. Production triggers, writes, authentication changes, and cron changes require explicit authorization.

For Harris Boat Works - Mercury Repower, treat the documented Node/Vite commands as repository setup instructions, not as proof of a particular MCP client integration.

_Full upstream README: https://allmcps.com/mcp/harris-boat-works-mercury-repower/readme_