Integration

Wavelength integration

Wavelength turns call notes, meeting transcripts and plain descriptions into editable process flow diagrams. Generate a flow from text with AI, create one from your own nodes and edges, list, search, read, update, duplicate and delete flows, edit a flow from a plain-English instruction, add notes, find gaps, write summaries and recaps, export as Mermaid, SVG, draw.io or JSON, and turn the public read-only link on or off. An organization key can also read the audit log and per-member usage. The agent payment route that buys a Pro pass is not exposed. Authentication is a Wavelength API key (starts with wlk_) sent as a Bearer token: a personal key (Settings, API keys; needs a paid plan or an organization seat; scopes flows:read and flows:write) acts as you on every flow you can open, an organization key (Organization settings, Security) acts on that organization's flows and can add audit:read and usage:read. AI calls (generate, edit, notes, summaries) and new flows count against the plan of the person who made the key. Limit: 600 requests per minute per key.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Wavelength.Built from the 18 Wavelength tools below, on the connection you add once.

What you can do with Wavelength

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Flow, 11 operations

  • add_notes_to_flowAdd notes to flowPOSTAgents: ask firstAdds new notes or transcript text to a flow with AI: steps already on the diagram are reused, new ones added, and the text is appended to the transcript. Returns the changed flow. Counts against the key owner's plan.
  • create_flowCreate flowPOSTAgents: ask firstCreates a flow from nodes and edges you send (no AI) and returns it with its id; nodes without x and y are laid out automatically. Use generate_flow to build one from text instead.
  • delete_flowDelete flowDELETEAgents: ask firstDeletes a flow. Returns deleted true and the flow id.
  • duplicate_flowDuplicate flowPOSTAgents: ask firstCopies a flow and returns the copy (with its new id).
  • edit_flow_with_aiEdit flow with aiPOSTAgents: ask firstChanges a flow with AI from a plain-English instruction (for example Add a manager approval before the refund), saves a version and returns the changed flow. Uses AI and counts against the key owner's plan.
  • export_flowExport flowGETAgents: ask firstExports a flow: format mermaid, svg or drawio returns the file as text in content; json returns graph_nodes and graph_edges.
  • generate_flowGenerate flowPOSTAgents: ask firstBuilds a new flow with AI from a transcript, call notes or a plain description (up to 100,000 characters), lays it out and returns it. Uses AI and counts against the key owner's plan.
  • get_flowGet flowGETAgents: ask firstReturns one flow with its nodes, edges, transcript and Mermaid code. A flow the key cannot open returns 404.
  • list_flowsList flowsGETAgents: ask firstLists the flows the key can open (a personal key: every flow you can open; an organization key: the organization's), newest change first, up to 200 per page. Page with offset = next_offset until next_offset is empty.
  • search_flowsSearch flowsGETAgents: ask firstSearches flow titles, steps and transcripts for a text (2 characters or more) and returns the matching flows with the matched steps and a transcript snippet.
  • update_flowUpdate flowPATCHAgents: ask firstChanges only the fields you send. graph_nodes and graph_edges must be sent together and replace the whole graph (read the flow first with get_flow). snapshot true keeps a version in the flow's history.

Flow public link, 2 operations

  • publish_flowPublish flowPOSTAgents: ask firstTurns on the flow's public read-only link and returns public_url: ANYONE with the link can view the flow. Optional summary is shown with it. Turn it off with unpublish_flow.
  • unpublish_flowUnpublish flowDELETEAgents: ask firstTurns off the flow's public read-only link, so the link stops working.

Api key, 1 operation

  • get_current_keyGet current keyGETAgents: ask firstReturns the API key in use (id, label, scopes, expiry, the email it acts as) and the organization it belongs to. Works with every key; use it to check which scopes are available.

Audit event, 1 operation

  • list_audit_eventsList audit eventsGETAgents: ask firstOrganization keys with audit:read only. Lists the organization's audit events newest first (membership, roles, settings, sharing, exports, public links, flow views, API key use, SCIM, billing), with actor emails.

Flow review, 1 operation

  • review_flowReview flowGETAgents: ask firstFinds gaps in a flow without AI cost: steps with no connection, dead ends, decisions with one branch, unlabeled branches, steps with no owner and AI-guessed links, plus questions to ask on the next call.

Flow summary, 1 operation

  • summarize_flowSummarize flowPOSTAgents: ask firstWrites a summary of a flow with AI: type overview returns summary and gaps; recaps returns customer_recap, handoff and leadership; systems_in_scope returns text listing each system with its inputs and outputs (no AI cost).

Usage, 1 operation

  • get_usageGet usageGETAgents: ask firstOrganization keys with usage:read only. Returns seats, totals and one row per member (AI calls, mic minutes, flows made, exports, last active time, two-step verification status) over 7, 30 or 90 days.

Use Wavelength from Claude Code, Cursor or Codex

Connect Wavelength in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Wavelength operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Wavelength

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Wavelength once

    Add your Wavelength connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Wavelength integration FAQ

What can you do with the Wavelength integration?

LiveContext exposes 18 operations on Wavelength, covering flow, flow public link, api key and audit event.

Popular integrations

Browse the whole catalog