Skip to main content
Book a demo

Connect Assembled to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Assembled to Claude Code in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Assembled’s 13 tools show up in Claude Code’s own tool list (supported Claude Code versions).

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

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

Tools

13 Assembled tools in Claude Code

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

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

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination