@codeam/shared 2.61.44 → 2.61.46

package/dist/index.mjs

@@ -827,6 +827,98 @@ var INTEGRATION_REGISTRY = {
       }
     }
   },
+  posthog: {
+    id: "posthog",
+    name: "PostHog",
+    icon: "posthog",
+    category: "observability",
+    // LIVE — api_key: the user pastes a PostHog Personal API Key (phx_…, created
+    // with the "MCP Server" preset). PostHog's MCP is HOSTED-ONLY
+    // (mcp.posthog.com) over HTTP, and its stdio bridge (mcp-remote) forces its
+    // own browser OAuth — incompatible with our headless broker. So delivery
+    // uses the shim's HTTP transport: it relays to the hosted MCP with the key
+    // as a Bearer header (exactly Cursor's {url, headers} config). No OAuth, no
+    // GSM secret; a backend VALIDATOR proves the key + vaults it.
+    enabled: true,
+    auth: {
+      kind: "api_key",
+      fields: [
+        {
+          key: "accessToken",
+          label: "Personal API Key",
+          placeholder: "phx_xxxxxxxxxxxxxxxx",
+          secret: true,
+          help: 'PostHog \u2192 Settings \u2192 Personal API keys \u2192 create with the "MCP Server" preset (scopes it to a project).'
+        }
+      ]
+    },
+    delivery: {
+      mcp: {
+        // HTTP transport (not a spawned stdio server) — the shim relays to
+        // PostHog's hosted MCP with the key as a Bearer header. The key stays
+        // server-side of the shim, never on argv.
+        command: "",
+        args: [],
+        envMapping: {},
+        httpUrl: "https://mcp.posthog.com/mcp",
+        httpHeaders: { Authorization: "Bearer {accessToken}" }
+      }
+    }
+  },
+  datadog: {
+    id: "datadog",
+    name: "Datadog",
+    icon: "datadog",
+    category: "observability",
+    // LIVE — api_key: the user pastes a Datadog API key (org-scoped) + an
+    // Application key (user-scoped, grants the read scopes) + their regional
+    // site. Datadog's OFFICIAL hosted MCP (mcp.<site>) accepts these as headers
+    // headless (verified) — no OAuth, no GSM secret. Delivery uses the shim's
+    // HTTP transport with the site templated into the URL and both keys sent as
+    // DD-API-KEY / DD-APPLICATION-KEY headers.
+    enabled: true,
+    auth: {
+      kind: "api_key",
+      fields: [
+        {
+          key: "accessToken",
+          label: "API Key",
+          placeholder: "Datadog API key",
+          secret: true,
+          help: "Organization API key \u2014 Datadog \u2192 Organization Settings \u2192 API Keys."
+        },
+        {
+          key: "appKey",
+          label: "Application Key",
+          placeholder: "Datadog application key",
+          secret: true,
+          help: "User Application key (grants the read scopes) \u2014 Datadog \u2192 Organization Settings \u2192 Application Keys."
+        },
+        {
+          key: "host",
+          label: "Site",
+          placeholder: "datadoghq.com",
+          secret: false,
+          help: "Your Datadog site \u2014 US1: datadoghq.com \xB7 EU: datadoghq.eu \xB7 US3: us3.datadoghq.com \xB7 US5: us5.datadoghq.com \xB7 AP1: ap1.datadoghq.com."
+        }
+      ]
+    },
+    delivery: {
+      mcp: {
+        // HTTP transport — the shim relays to Datadog's hosted MCP for the
+        // user's site, with both keys as headers. Keys stay server-side of the
+        // shim, never on argv.
+        command: "",
+        args: [],
+        envMapping: {},
+        httpUrl: "https://mcp.{host}/api/unstable/mcp-server/mcp",
+        httpHeaders: {
+          "DD-API-KEY": "{accessToken}",
+          "DD-APPLICATION-KEY": "{appKey}"
+        }
+      }
+    }
+  },
   notion: {
     id: "notion",
     name: "Notion",
@@ -1231,7 +1323,6 @@ var INTEGRATION_BRANDING = {
 };
 var UPCOMING_INTEGRATION_IDS = [
   "gmail",
-  "posthog",
   "clickup",
   "figma",
   "trello",
@@ -1244,8 +1335,7 @@ var UPCOMING_INTEGRATION_IDS = [
   "mixpanel",
   "pendo",
   "pagerduty",
-  "amplitude",
-  "datadog"
+  "amplitude"
 ];
 function getIntegrationBranding(id) {
   return INTEGRATION_BRANDING[id] ?? null;