Skip to main content

Connect Sigma to Claude Cowork

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

Set up

Add Sigma to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.

  1. 1

    Add Sigma to Runlayer

    Sigma 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 Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Sigma’s 7 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Sigma

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

  4. 4

    Use Sigma from Claude Cowork

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

Tools

7 Sigma tools in Claude Cowork

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

  • Begin session

    REQUIRED — You MUST call this tool before using any other Sigma tool in a conversation.

  • Call agent

    Call a Sigma workbook agent with a message or conversation.

  • Describe

    Inspect the schema of a Sigma data source.

  • List documents

    Browse a named document collection in the Sigma workspace.

  • List workbook agents

    List the workbook agents you can edit across your organization

  • Query

    Execute a SQL query against a Sigma data source and return the results.

  • Search

    Search across the entire Sigma workspace to discover workbooks, data models, data model elements, and tables.

Control

What Runlayer can see and stop in Claude Cowork

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

  • Gateway policy (available)

    Every Sigma call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork 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)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination