Skip to main content
Book a demo

Connect Collate to Codex

Give Codex governed access to Collate’s 19 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Collate to Codex in four steps

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

  1. 1

    Add Collate to Runlayer

    Collate isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Collate’s 19 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Collate

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

  4. 4

    Use Collate from Codex

    Collate’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

19 Collate tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Create article

    Creates a Knowledge Center Article page in Collate.

  • Create classification

    Creates a new Classification in OpenMetadata.

  • Create data product

    Creates a new Data Product in OpenMetadata.

  • Create domain

    Creates a new Domain in OpenMetadata.

  • Create glossary

    Creates a new Glossary.

  • Create glossary term

    Creates a new Glossary Term.

  • Create lineage

    Can be used to create lineage between two assets.

  • Create metric

    Creates a new Metric entity in OpenMetadata.

See all 19 Collate tools

Control

What Runlayer can see and stop in Codex

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

  • Gateway policy (available)

    Every Collate call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex 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 or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination