Skip to main content

Connect Lucid to Warp

Give Warp governed access to Lucid’s 42 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Lucid to Warp in four steps

Admins approve the server once. Everyone in Warp then gets it through the same governed connection.

  1. 1

    Approve Lucid in Runlayer

    Add Lucid from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Warp to Runlayer

    Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Lucid’s 42 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Warp setup guide
  3. 3

    Sign in to Lucid

    Sign in the way Lucid requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Lucid from Warp

    Lucid’s approved tools appear in Warp. Every call is checked against policy and recorded.

Tools

42 Lucid tools in Warp

Runlayer policy decides which of these Warp users can call. 2 read data only.

  • Create embed

    Internal tool for MCP Apps extension only.

  • Create embed session token

    Internal tool for MCP Apps extension only.

  • Exchange legacy embed session

    Internal tool for MCP Apps extension only.

  • Fetch Lucid document content

    Retrieves the structured content of a specific Lucid document by its ID.

  • Get MCP resource

    Reads a resource from this MCP server by URI.

  • List document thread comments

    List comments on a specific collaboration thread of a Lucid document.

  • List document threads

    List collaboration threads on a Lucid document.

  • Add block

    Add a new block (shape) to a Lucid document.

See all 42 Lucid tools

Control

What Runlayer can see and stop in Warp

Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.

  • Gateway policy (available)

    Every Lucid call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination