Skip to main content
Book a demo

Connect Gumloop to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Gumloop 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

    Approve Gumloop in Runlayer

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

  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, Gumloop’s 45 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Gumloop

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

  4. 4

    Use Gumloop from Claude Code

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

Tools

45 Gumloop tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • List agents

    List agents in your Gumloop account, with optional search and workspace filtering.

  • Get agent

    Fetch a single Gumloop agent's configuration by its ID.

  • Ask gummie

    Ask questions and get AI-powered answers from Gumloop documentation.

  • Attach agent MCP server

    Attach an MCP server (connector) to a Gumloop agent, or update its configuration if already attached.

  • Attach agent skills

    Attach one or more existing skills to a Gumloop agent.

  • Call MCP tool

    Execute a single tool on a connected MCP server.

  • Cancel session

    Cancel an in-progress Gumloop agent session.

  • Create agent

    Create a new Gumloop agent with a name, model, and optional configuration.

See all 45 Gumloop 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 Gumloop 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