@codeam/shared 2.61.43 → 2.61.45

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.mjs CHANGED
@@ -788,6 +788,83 @@ var INTEGRATION_REGISTRY = {
788
788
  }
789
789
  }
790
790
  },
791
+ resend: {
792
+ id: "resend",
793
+ name: "Resend",
794
+ icon: "resend",
795
+ category: "comms",
796
+ // LIVE — api_key (like Azure DevOps): the user pastes a Resend API key
797
+ // (`re_…`); Resend has NO OAuth, so there's no OAuth app / GSM secret /
798
+ // config-gated 503 — a backend VALIDATOR proves the key against the Resend
799
+ // API and vaults it. ⚠️ SEND-ONLY email → `sendOnly: true` keeps it OUT of
800
+ // From-Conversation (comms conversation sources need readable threads; Resend
801
+ // has none) while still being a linkable comms tool the agent uses via MCP.
802
+ enabled: true,
803
+ sendOnly: true,
804
+ auth: {
805
+ kind: "api_key",
806
+ fields: [
807
+ {
808
+ key: "accessToken",
809
+ label: "API Key",
810
+ placeholder: "re_xxxxxxxxxxxxxxxx",
811
+ secret: true,
812
+ help: 'Create in Resend \u2192 API Keys (https://resend.com/api-keys). "Sending access" is enough.'
813
+ }
814
+ ]
815
+ },
816
+ delivery: {
817
+ mcp: {
818
+ // The OFFICIAL resend-mcp (Node) in BYO-token mode: the API key is fed
819
+ // via RESEND_API_KEY (env only, never argv). Version PINNED; bump only
820
+ // after re-verifying headless. Tools: send email + contacts/broadcasts/
821
+ // domains.
822
+ command: "npx",
823
+ args: ["-y", "resend-mcp@2.6.1"],
824
+ envMapping: {
825
+ RESEND_API_KEY: "accessToken"
826
+ }
827
+ }
828
+ }
829
+ },
830
+ posthog: {
831
+ id: "posthog",
832
+ name: "PostHog",
833
+ icon: "posthog",
834
+ category: "observability",
835
+ // LIVE — api_key: the user pastes a PostHog Personal API Key (phx_…, created
836
+ // with the "MCP Server" preset). PostHog's MCP is HOSTED-ONLY
837
+ // (mcp.posthog.com) over HTTP, and its stdio bridge (mcp-remote) forces its
838
+ // own browser OAuth — incompatible with our headless broker. So delivery
839
+ // uses the shim's HTTP transport: it relays to the hosted MCP with the key
840
+ // as a Bearer header (exactly Cursor's {url, headers} config). No OAuth, no
841
+ // GSM secret; a backend VALIDATOR proves the key + vaults it.
842
+ enabled: true,
843
+ auth: {
844
+ kind: "api_key",
845
+ fields: [
846
+ {
847
+ key: "accessToken",
848
+ label: "Personal API Key",
849
+ placeholder: "phx_xxxxxxxxxxxxxxxx",
850
+ secret: true,
851
+ help: 'PostHog \u2192 Settings \u2192 Personal API keys \u2192 create with the "MCP Server" preset (scopes it to a project).'
852
+ }
853
+ ]
854
+ },
855
+ delivery: {
856
+ mcp: {
857
+ // HTTP transport (not a spawned stdio server) — the shim relays to
858
+ // PostHog's hosted MCP with the key as a Bearer header. The key stays
859
+ // server-side of the shim, never on argv.
860
+ command: "",
861
+ args: [],
862
+ envMapping: {},
863
+ httpUrl: "https://mcp.posthog.com/mcp",
864
+ httpHeaders: { Authorization: "Bearer {accessToken}" }
865
+ }
866
+ }
867
+ },
791
868
  notion: {
792
869
  id: "notion",
793
870
  name: "Notion",
@@ -1192,11 +1269,9 @@ var INTEGRATION_BRANDING = {
1192
1269
  };
1193
1270
  var UPCOMING_INTEGRATION_IDS = [
1194
1271
  "gmail",
1195
- "posthog",
1196
1272
  "clickup",
1197
1273
  "figma",
1198
1274
  "trello",
1199
- "resend",
1200
1275
  "vercel",
1201
1276
  "supabase",
1202
1277
  "asana",