Connecting an MCP Client

Waymaker runs a remote MCP server at https://mcp.waymakerone.com/mcp. Any MCP-compatible client connects the same way — no local process to run, nothing to install.

1. Get an API key

Mint one at admin.waymakerone.com/api/keys — see Authentication.

2. Configure your client

Claude Desktop

Open Settings → Developer → Edit Config, and add the waymaker block to claude_desktop_config.json:

{
  "mcpServers": {
    "waymaker": {
      "type": "http",
      "url": "https://mcp.waymakerone.com/mcp",
      "headers": {
        "Authorization": "Bearer wm_sk_YOUR_KEY"
      }
    }
  }
}

Quit and reopen Claude Desktop completely (not just close the window) for it to pick up the change.

Claude Code

Create .mcp.json in your project root (add it to .gitignore):

{
  "mcpServers": {
    "waymaker": {
      "type": "http",
      "url": "https://mcp.waymakerone.com/mcp",
      "headers": {
        "Authorization": "Bearer wm_sk_YOUR_KEY"
      }
    }
  }
}

Claude Code reads MCP servers from .mcp.json at the project root — not from .claude/settings.json. Restart Claude Code after saving.

Cursor

Same block, in .cursor/mcp.json (project-level) or your global Cursor MCP settings.

3. Verify

Start a new chat and ask: "What Waymaker tools are available?" You should see tools listed — which ones depends on your key's permissions (see below). See the tool catalogue for what's there.

How your key's permissions map to MCP

MCP collapses your key's ticked permissions into two effective scopes: any :read permission grants MCP read, and :write/:deploy/:admin grant MCP write (which implies read). A key with only :read permissions won't show write-shaped tools at all, not even as disabled.

sync:read/sync:write do not currently grant the MCP sync scope — a naming mismatch on the server side, not something you can work around from the key's permissions. The handful of MCP tools that require sync are effectively unreachable today. See Authentication → Permissions for the full list of what a key can carry.

Tool-list caching

Your client calls tools/list once, when the connection is established, and caches the result for the session. If you change your API key's permissions (or swap keys), reconnect the client — restart Claude Desktop, or start a new Claude Code / Cursor session — rather than expecting the tool list to update mid-session.

Unlisted arguments are ignored, not rejected

A tool's inputSchema lists the arguments it actually reads. Passing an argument that isn't in that schema doesn't error — the tool simply never reads it, so it has no effect. If something you're asking the assistant to pass doesn't seem to be doing anything, check it's actually a declared parameter of that tool (see the tool catalogue).

Partners: one key per client

Each API key is scoped to one organization. If you manage multiple clients, use a separate key — and a separate MCP config — per client, never one global config for all of them.

Next steps

• Tool catalogue
• Authentication