Skip to main content
Book a demo

Connect Navattic to Claude

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

Book a demo Claude setup guide

Set up

Add Navattic to Claude in four steps

Admins approve the server once. Everyone in Claude 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 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, Navattic’s 62 tools show up in Claude’s own tool list.

    Claude 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

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

Tools

62 Navattic tools in Claude

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

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

  • Gateway policy (available)

    Every Navattic 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