Skip to main content
Book a demo

Connect Assembled to Warp

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

Book a demo Warp setup guide

Set up

Add Assembled to Warp in four steps

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

  1. 1

    Add Assembled to Runlayer

    Assembled isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Warp to Runlayer

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

    Warp setup guide
  3. 3

    Sign in to Assembled

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

  4. 4

    Use Assembled from Warp

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

Tools

13 Assembled tools in Warp

Runlayer policy decides which of these Warp users can call.

  • Create forecast adjustments

    Create one or more forecast adjustments layered on the master forecast.

  • Create overtime and voluntary time off

    Publish one overtime ('OT') or voluntary-time-off ('VTO') slot.

  • Get agent time summaries

    Approved overtime (overtime_seconds),

  • Get bpo heatmap

    Get BPO staffing per time bucket: required, committed, scheduled and actuals.

  • Get current time

    Get the current date and time, in both UTC and the company's timezone.

  • Get forecast adjustments

    List existing forecast adjustments for the company.

  • Get forecasted vs actual

    Get forecasted vs actual comparison metrics from Assembled.

  • Get metrics catalog and query usage

    Get the catalog of available metrics and instructions for using the query_metrics() tool.

See all 13 Assembled 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 Assembled 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