Waymaker
WaymakerDocs
Developer Documentation
Documentation

Quick Start

CLI and MCP authenticate with the same API key. .ctx doesn't need one — see step 4. Mint a key first if you're using the CLI or MCP.

1. Get an API key

  1. Sign in at admin.waymakerone.com
  2. Go to /api/keys
  3. Click Create API Key, name it, and tick permissions (everything but host:admin is ticked by default)
  4. Copy the key — it starts with wm_sk_ and is shown once

See Authentication for what each permission grants.

2. CLI

npm install -g @waymakeros/cli
export WAYMAKER_API_KEY=wm_sk_your_key_here   # or add it to a .env file
waymaker auth status
waymaker workspaces list
waymaker taskboards list

Full guide: CLI Installation.

3. MCP

Add Waymaker as an MCP server in Claude Desktop, Claude Code, or Cursor:

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

Restart the client, then ask it: "What Waymaker tools are available?"

Full guide: Connecting an MCP client.

4. .ctx

Inside an Ambassador, .ctx is already authenticated as a server-side context scoped to that app — no API key needed there. It's the scoped read/write surface for platform data, for example:

export default async function handler(req, ctx) {
  const bucket = ctx.storage.bucket('customer-uploads')
  await bucket.put('report.pdf', bytes, { contentType: 'application/pdf' })
}

Full guide: .ctx overview.

Next steps