Luma

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Luma's real ids.

{
  "manifestVersion": "2",
  "name": "luma-example",
  "steps": [
    {
      "id": "calendar-events-add",
      "uses": {
        "app": "io.w6w.luma",
        "action": "calendar-events-add",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "platform": "<platform>"
      }
    }
  ]
}

Here are some of the things you can do

• Add Event to Calendar

  perform
  calendar-events-add

• List Calendar Admins

  search
  calendar-admins-list

• Approve Calendar Event Submission

  perform
  calendar-events-approve

• List Calendar Events

  search
  calendar-events-list

• Lookup Calendar Event Submission

  read
  calendar-events-lookup

+24 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Luma, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Luma. The Workflow tab is where this app's real ids are.

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "calendar-events-add",
  payload: {
    platform: "<value>",
    // submissionMode: "<value>",
    // eventId: "<value>",
    // url: "<value>",
    // name: "<value>",
    // startAt: "<value>",
    // durationInterval: "<value>",
    // timezone: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

npm install -g @w6w/cli

w6w run conn_YOUR_CONNECTION_ID --action calendar-events-add --payload '{"platform":"<value>"}'

Give an AI agent Luma — without giving it Luma's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.luma#calendar-events-add",
    "input": {
      "platform": "<platform>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Luma connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

The MCP surface is part of the hosted platform. Luma itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access