Skip to main content
Book a demo

Connect Assembled to Claude

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

Book a demo Claude setup guide

Set up

Add Assembled to Claude in four steps

Admins approve the server once. Everyone in Claude 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 Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Assembled’s 13 tools show up in Claude’s own tool list.

    Claude 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 Claude

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

Tools

13 Assembled tools in Claude

Runlayer policy decides which of these Claude 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 Claude

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination