Skip to main content

Connect Datadog to OpenCode

Give OpenCode governed access to Datadog’s 414 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Datadog to OpenCode in four steps

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

  1. 1

    Approve Datadog in Runlayer

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

  2. 2

    Connect OpenCode to Runlayer

    Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Datadog’s 414 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    OpenCode setup guide
  3. 3

    Sign in to Datadog

    Each user signs in to Datadog with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Datadog from OpenCode

    Datadog’s approved tools appear in OpenCode. Every call is checked against policy and recorded.

Tools

414 Datadog tools in OpenCode

Runlayer policy decides which of these OpenCode users can call.

  • Dd gff

    Do-not-call

  • Dd guc

    Do-not-call

  • Dd rfw

    Do-not-call

  • Dd wfd

    Do-not-call

  • Aap get activation options

    Aap get activation options.

  • Aap onboarding

    Returns the authoritative step-by-step instructions for enabling Datadog App and API Protection (AAP) to monitor and secure your application.

  • Add comment to Datadog case

    Add a comment to a Datadog Work Item (also called a Case) timeline.

  • Add llmobs annotation queue interactions

    Queue traces, sessions, or spans for human review in an annotation queue.

See all 414 Datadog tools

Control

What Runlayer can see and stop in OpenCode

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination