Connect Claude, ChatGPT, or any MCP client to the Boat Owner MCP. Your agent finds vetted marine pros, starts owner-verified service requests, compares the responses, and moves the work forward — from one public endpoint, no API key.

MCP clients discover the Boat Owner MCP tools straight from the server. Add the endpoint once, then just ask your agent to find marine pros or compare public storefronts — it picks the right tool on its own.
Our own AI assistant runs on the Boat Owner MCP out of the box — the fastest way to find a pro and start a request, with nothing to configure.
claude mcp add --transport http \ boatwork-search \ https://mcp.boatwork.co/boat-owner-mcp
One line and you’re connected. Tools show up the moment your client refreshes.
{
"mcpServers": {
"boatwork-search": {
"url": "https://mcp.boatwork.co/boat-owner-mcp"
}
}
}Any client that speaks remote HTTP MCP works. Some also accept "type": "http".
Discovery stays public and read-only. The moment work becomes real, the owner verifies by email — so an agent can explore freely without ever surprising a customer.
A confirmed request becomes a real opportunity. From there it’s the same record a pro’s agent works on the Pro MCP — responses, visits, and estimates all flow back to this side automatically.
See the Pro MCPThe short answers most teams ask before wiring up the endpoint.
No. The Boat Owner MCP is public. Search and storefront tools are anonymous, and service requests use owner consent plus email verification instead of keys.
No. The first step only creates a draft and emails the boat owner. Pros are contacted only after the owner confirms with the code.
The Boat Owner MCP is the boater, demand-side surface. The Pro MCP is the pro, supply-side surface and needs a pro-scoped bearer token. Both work the same opportunity.
Any client that supports remote HTTP MCP servers — Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT Apps & Connectors, and custom agents.