@integrity-labs/agt-cli 0.28.1112 → 0.28.1114

package/dist/{chunk-NO57I56V.js → chunk-OBZB6MUE.js}

@@ -2049,6 +2049,34 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.kajabi.com/articles/api-integrations/connect-kajabi-to-claude-or-chatgpt",
     beta: true
   },
+  {
+    id: "otter",
+    name: "Otter.ai",
+    category: "knowledge",
+    description: "Read Otter.ai meetings: search recordings by date, attendee or topic, and read summaries, action items and full speaker-attributed transcripts.",
+    // CS-2029: same remote streamable-HTTP MCP + OAuth pattern as Granola/Kajabi.
+    // Otter's server implements the MCP discovery chain (RFC 9728 protected-
+    // resource metadata at mcp.otter.ai → RFC 8414 AS metadata at otter.ai →
+    // RFC 7591 registration); auth is OAuth 2.0 authorization-code with PKCE
+    // (S256) and a public client registered via one-time Dynamic Client
+    // Registration (scripts/dcr-register.ts against https://otter.ai/oauth/register
+    // → OAUTH_OTTER_CLIENT_ID, --scope 'profile:read conversations:read').
+    // Consent is brokered by the webapp through the shared
+    // /integrations/oauth/authorize → /callback path, and the access_token
+    // reaches the host via the generic remote-oauth-proxy
+    // (OAUTH_PROVIDERS.otter.mcpUrl). Read-only by construction: Otter
+    // advertises no write scope.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "otter:read", name: "Read Meetings & Transcripts", description: "Find recorded meetings by date, attendee, topic or title, and read their summaries, action items, outlines and full transcripts (otter_get_user_info, otter_search, otter_fetch)", access: "read" }
+    ],
+    // Otter's own Help Center article for the MCP server (CodeRabbit, #6906). It
+    // exists even though help.otter.ai answers 403 to non-browser clients; the
+    // help-centre API confirmed it (title "Otter MCP Server"). The MCP endpoint
+    // itself is a JSON-RPC URL, not a page (Obi Wan 8305072d5414).
+    docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",
@@ -11725,6 +11753,51 @@ var OAUTH_PROVIDERS = {
       }
     ]
   },
+  "otter": {
+    // CS-2029: Otter.ai's official MCP — remote streamable-HTTP at
+    // https://mcp.otter.ai/mcp. Same Granola/Kajabi shape: OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client
+    // (token_endpoint_auth_method 'none') issued via Dynamic Client
+    // Registration (RFC 7591). Values below are taken verbatim from the
+    // metadata, not inferred:
+    //   - https://mcp.otter.ai/.well-known/oauth-protected-resource names the
+    //     AS as https://otter.ai/ and advertises scopes profile:read,
+    //     conversations:read;
+    //   - https://otter.ai/.well-known/oauth-authorization-server gives
+    //     authorize /oauth2/authorize, token /oauth/token, revoke
+    //     /oauth/revoke_token, register /oauth/register, PKCE S256, `none`,
+    //     and the refresh_token grant.
+    // NOTE the authorize path is /oauth2/authorize while token/revoke live
+    // under /oauth/ — that is Otter's own split, do not "normalise" it.
+    // The prod client was registered 2026-10-10 against /oauth/register with
+    // scope 'profile:read conversations:read' and BOTH API callbacks,
+    // https://api.augmented.team/... and https://api.ninjafy.com/integrations/oauth/callback,
+    // because redirect_uri follows API_PUBLIC_URL and the ENG-11060 flip makes
+    // the ninjafy name canonical; Otter returns no RFC 7592 handle, so a redirect
+    // cannot be added later without a new client and a re-consent per connection.
+    // OAUTH_OTTER_CLIENT_ID is set from its output (docs/runbooks/otter-dogfood.md). Otter advertises ONLY
+    // read scopes, so this integration is read-only by construction: there is
+    // no write scope to request even by mistake.
+    definitionId: "otter",
+    authorizeUrl: "https://otter.ai/oauth2/authorize",
+    tokenUrl: "https://otter.ai/oauth/token",
+    revokeUrl: "https://otter.ai/oauth/revoke_token",
+    defaultScopes: ["profile:read", "conversations:read"],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.otter.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // These are the server's three tools, all read-only. The names are
+    // Otter's own, quoted from the tools' descriptions ("use `otter_search`
+    // first", "call otter_get_user_info() first"), not Composio's wrapped
+    // OTTER_AI_MCP_* slugs. An allowlisted name the server does not advertise
+    // is logged and SKIPPED by the proxy, so confirm against the first live
+    // tools/list after a real consent (runbook Step 3).
+    toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -16626,4 +16699,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-NO57I56V.js.map
+//# sourceMappingURL=chunk-OBZB6MUE.js.map