Datadog

Add the connection from eve's registry. This writes the initial definition under agent/connections/ and installs its authentication dependency when needed:

eve add connection/datadog

Create agent/connections/datadog.ts. The connection name is derived from the filename:

// agent/connections/datadog.tsimport { connect } from "@vercel/connect/eve";import { defineMcpClientConnection } from "eve/connections";
export default defineMcpClientConnection({  url: "https://mcp.datadoghq.com/api/mcp",  description: "Datadog: query metrics, monitors, logs, and incidents.",  auth: connect({    connector: "datadog",    principalToSubject: (principal) => {      const email = principal.type === "user" ? principal.attributes?.email : undefined;      if (typeof email !== "string") {        throw new Error("JWT bearer authentication requires a user principal with an email.");      }      return { type: "jwt-bearer", sub: email };    },  }),});

Connect exchanges a JWT bearer assertion for a provider token. principalToSubject maps each principal to the subject your IdP expects.

Link your project, create the connector, and pull OIDC locally:

vercel linkvercel connect create datadogvercel env pull

For JWT bearer, principalToSubject controls the asserted subject. The default maps app principals to { type: "app" } and user principals to { type: "user", id, issuer }.

Match the MCP url to your Datadog site (datadoghq.com, datadoghq.eu, and so on).

See the Connections docs for principal types, headers, approval, and protocol-specific filters.