Skip to main content
Book a demo

Connect Neon to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Neon 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

    Approve Neon in Runlayer

    Add Neon from the catalog and choose who can use it and which of its tools are allowed.

  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, Neon’s 29 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Neon

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

  4. 4

    Use Neon from Claude Cowork

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

Tools

29 Neon tools in Claude Cowork

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

  • List projects

    Lists the first 10 Neon projects in your account.

  • List organizations

    Lists all organizations that the current user has access to.

  • List shared projects

    Lists projects that have been shared with the current user.

  • Create project

    Create a new Neon project.

  • Delete project

    Delete a Neon project

  • Describe project

    Describes a Neon project

  • Run SQL

    Execute a single SQL statement against a Neon database.

  • Run SQL transaction

    Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.

See all 29 Neon tools

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 Neon 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