YachtMaster

cloud.yachtmasterPublished by yachtmaster.cloudOfficial publisherv1.0.0Updated Oct 26, 2026

Operate a YachtMaster ERP tenant: boats, offers, projects, hours and invoicing.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant operate a YachtMaster ERP tenant: boats, offers, projects, hours and invoicing.

What you can do
  • Manage boats and offers in the ERP tenant
  • Work with projects and recorded hours
  • Handle invoicing through the connected YachtMaster account
  • No tool list is published, so the exact operations are not documented here.
When to use it
Useful when a team already runs its boat-rental or charter business on YachtMaster and wants an assistant to read or update that ERP data without switching apps.
Requirements
A remote MCP endpoint at app.yachtmaster.cloud reached over streamable HTTP; OAuth sign-in to a YachtMaster tenant is required. No environment variables or headers are declared.
Before you install
The server works on live business records such as offers, projects, hours and invoices, so assistant actions may create or change data and affect billing. Access is granted through OAuth to a tenant account; review the scopes granted. No tool list is published, so verify what it can modify before use.

Installation

In SourceWeft

  1. Open YachtMaster in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cloud.yachtmaster%2Ferp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "yachtmaster": {
      "type": "http",
      "url": "https://app.yachtmaster.cloud/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.