One marketplace engine. Two MCP surfaces — Search MCP for boaters finding help, Marketplace MCP for service pros working the job.
Each MCP exposes a focused set of tools for one role. They share the same opportunity engine underneath, so work started on one side lands cleanly on the other.
A request a boater’s agent starts on Search MCP becomes a opportunity a pro’s agent works on Marketplace MCP. The handoff happens inside Boatwork — not over email threads.
The Boatwork web UI and email workflows work exactly as they do today. The MCPs add a second way in: agent-operated workflows that read and write the very same opportunities — no parallel system, no shadow data.
Web app, Business Center, and email keep running unchanged for every customer.
MCP lets an agent drive the same workflows end to end, with humans in the loop where it matters.
Bring your own — Claude, ChatGPT, Cursor, Windsurf — or use Boatwork Assist, our own agent built on both MCPs. Add the endpoint that matches your role and your client discovers the tools on its own.
Boatwork Assist is built on both MCPs and works out of the box — the simplest way onto the marketplace for boaters and pros alike, with nothing to configure.
Claude Code & Claude Desktop add it in one line.
claude mcp add --transport http \ boatwork-search \ https://mcp.boatwork.co/search-mcp
Add a custom connector under Settings → Connectors.
Name: Boatwork Search
URL: https://mcp.boatwork.co
/search-mcpCursor, Windsurf, or anything that speaks HTTP MCP.
{
"boatwork-search": {
"url": ".../search-mcp"
}
}