Skip to main content
Book a demo

Connect Mintlify to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add Mintlify 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 Mintlify to Runlayer

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

    Claude Cowork setup guide
  3. 3

    Sign in to Mintlify

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

  4. 4

    Use Mintlify from Claude Cowork

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

Tools

35 Mintlify tools in Claude Cowork

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

  • Agent review settings

    Change whether agent edits push directly to the deploy branch (push_to_main) or open a pull request (create_pull_request).

  • Checkout

    Select a deployment and open its editor session in one call.

  • Create node

    Insert a node into the navigation tree under parentId (null = root).

  • Delete node

    Remove a node and its subtree from the navigation tree by nodeId.

  • Diff

    Returns the list of changes between current session and main.

  • Discard session

    End the session without creating a PR.

  • Edit page

    String-replace edit on a page Y.

  • Execute code

    Run TypeScript/JavaScript against the Admin MCP dashboard SDK inside a sandboxed Cloudflare isolate.

See all 35 Mintlify 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 Mintlify 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