Skip to main content

Connect Great Question to Cline CLI

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

Set up

Add Great Question to Cline CLI in four steps

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

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Great Question’s 132 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

132 Great Question tools in Cline CLI

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

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

  • Gateway policy (available)

    Every Great Question call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination