Skip to main content
Book a demo

Connect Navattic to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Navattic 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 Navattic to Runlayer

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

    Claude Code setup guide
  3. 3

    Sign in to Navattic

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

  4. 4

    Use Navattic from Claude Code

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

Tools

62 Navattic tools in Claude Code

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

  • Create brain asset

    Add a URL, FILE, or TEXT asset to an agent's brain.

  • Create launchpad share link

    Create a launchpad share link, sourced from either a set of custom flows or a demo.

  • Delete brain asset

    Permanently delete a Brain asset.

  • Get account

    Get a detailed profile for a specific company account by ID.

  • Get agent demo

    Get a Navattic agent's configuration — objective, personality, tone, FAQs, pronunciations, CTA, welcome screen, language, voice, avatar, escalation/interruption flags, and the linked environment.

  • Get agent demo session

    Get full details for a Navattic agent session: parsed transcript turns, qualifications, summary, sentiment, signals detected, outcome reached, status, end user, and the Steel session viewer URL for…

  • Get agent environment

    Get an agent environment and its folder/flow tree.

  • Get demo

    Get a specific demo.

See all 62 Navattic 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 Navattic 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