Skip to main content
Book a demo

Connect Great Question to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Great Question 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 Great Question to Runlayer

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

    Claude Code setup guide
  3. 3

    Sign in to Great Question

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

  4. 4

    Use Great Question from Claude Code

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

Tools

132 Great Question tools in Claude Code

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

  • Add interview moderator

    Add a new interview moderator.

  • Add interview participant

    Add a new interview participant.

  • Add interview screener Question

    Add a new interview screener question.

  • Add study participant

    Add a new study participant.

  • Add survey participant

    Add a new survey participant.

  • Add survey Question

    Add a new survey question.

  • Add survey screener Question

    Add a new survey screener question.

  • Add unmoderated participant

    Add a new unmoderated participant.

See all 132 Great Question 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 Great Question 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