@integrity-labs/agt-cli 0.28.1130 → 0.28.1132

package/dist/mcp/index.js

@@ -25624,6 +25624,61 @@ var OAUTH_PROVIDERS = {
     // tools/list after a real consent (runbook Step 3).
     toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
   },
+  "plaud": {
+    // ENG-11543 (CS-2134): Plaud's hosted MCP - remote streamable-HTTP at
+    // https://mcp.plaud.ai/mcp. Same Granola/Kajabi/Otter 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). NOT the stdio `npx @plaud-ai/mcp` package,
+    // which runs its own local browser sign-in and token file. Values below
+    // are taken verbatim from the metadata (re-read 2026-10-16), not inferred:
+    //   - https://mcp.plaud.ai/.well-known/oauth-protected-resource (and the
+    //     path-suffixed /.well-known/oauth-protected-resource/mcp the server's
+    //     401 points at) give resource https://mcp.plaud.ai/mcp, AS
+    //     https://mcp.plaud.ai/, bearer in the header;
+    //   - https://mcp.plaud.ai/.well-known/oauth-authorization-server (and
+    //     the identical openid-configuration) give authorize /authorize, token
+    //     /token, register /register, PKCE S256 only, `none` among the token
+    //     auth methods, and the authorization_code + refresh_token grants.
+    // NOT advertised: `scopes_supported` (so defaultScopes is empty, the
+    // notion-cli precedent, and the authorize URL carries `scope=`) and
+    // `revocation_endpoint` (so there is no revokeUrl: disconnecting here
+    // deletes our copy of the token but cannot revoke Plaud's grant; the user
+    // revokes it in their Plaud account).
+    //
+    // DCR (operator step, NOT done as of this commit): POST the registration
+    // body by hand to https://mcp.plaud.ai/register with client_name
+    // `Ninjafy`, token_endpoint_auth_method `none`, grant_types
+    // authorization_code + refresh_token, and BOTH API callbacks in
+    // redirect_uris (https://api.augmented.team/integrations/oauth/callback
+    // and https://api.ninjafy.com/integrations/oauth/callback). Do not use
+    // scripts/dcr-register.ts: it takes a single --redirect-uri. Store the
+    // returned client id as OAUTH_PLAUD_CLIENT_ID; unset, Connect soft-fails
+    // "not configured". Full procedure: docs/runbooks/plaud-dogfood.md.
+    definitionId: "plaud",
+    authorizeUrl: "https://mcp.plaud.ai/authorize",
+    tokenUrl: "https://mcp.plaud.ai/token",
+    defaultScopes: [],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.plaud.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // Plaud advertises NO scopes, so the token is not scope-limited: the
+    // read-only property of this integration rests ENTIRELY on this
+    // allowlist, which the remote-oauth-proxy enforces on tools/list and
+    // tools/call. The five names are Plaud's documented read tools
+    // (https://docs.plaud.ai/plaud-mcp-cli/mcp). `login` and `logout` are
+    // deliberately excluded: sign-in is our OAuth broker's job, and `logout`
+    // revokes the user's authorization, which an agent must never do. The
+    // names come from the docs, not from an authenticated tools/list (that
+    // needs a consented token), and the proxy SKIPS an allowlisted name the
+    // server does not serve, so confirm against the first live tools/list
+    // (runbook Step 3, a gate before customer use).
+    toolAllowlist: ["get_current_user", "list_files", "get_file", "get_note", "get_transcript"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -26080,6 +26135,36 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
     beta: true
   },
+  {
+    id: "plaud",
+    name: "Plaud",
+    category: "knowledge",
+    description: "Read Plaud recordings: list and search recordings by name or date, and read their AI notes (summary, action items, key topics) and full speaker-labelled transcripts.",
+    // ENG-11543 (CS-2134): same remote streamable-HTTP MCP + OAuth pattern as
+    // Granola/Kajabi/Otter, against Plaud's HOSTED server (https://mcp.plaud.ai/mcp),
+    // not the stdio `npx @plaud-ai/mcp` package. Discovery chain: RFC 9728
+    // protected-resource metadata at mcp.plaud.ai -> RFC 8414 AS metadata on the
+    // same host -> RFC 7591 registration at /register. Auth is OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client registered once by
+    // an operator (docs/runbooks/plaud-dogfood.md -> OAUTH_PLAUD_CLIENT_ID).
+    // Consent is brokered through the shared /integrations/oauth/authorize ->
+    // /callback path, and the token reaches the host via the generic
+    // remote-oauth-proxy (OAUTH_PROVIDERS.plaud.mcpUrl).
+    //
+    // READ-ONLY RESTS ENTIRELY ON THE TOOL ALLOWLIST. Unlike Otter, Plaud
+    // advertises NO scopes_supported, so there is no read scope to request and
+    // the granted token is not scope-limited. What keeps this integration
+    // read-only is OAUTH_PROVIDERS.plaud.toolAllowlist (the five documented
+    // reads), which the proxy enforces on tools/list and tools/call. `login` and
+    // `logout` are excluded; `logout` would revoke the user's authorization.
+    // Anything that widens the allowlist widens what the token can do.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "plaud:read", name: "Read Recordings & Transcripts", description: "List and search recordings by name or date, and read their details, AI notes (summary, action items, key topics) and full transcripts with speaker labels (get_current_user, list_files, get_file, get_note, get_transcript)", access: "read" }
+    ],
+    docs_url: "https://docs.plaud.ai/plaud-mcp-cli/mcp",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",

package/dist/mcp/origami.js

@@ -39756,6 +39756,61 @@ var OAUTH_PROVIDERS = {
     // tools/list after a real consent (runbook Step 3).
     toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
   },
+  "plaud": {
+    // ENG-11543 (CS-2134): Plaud's hosted MCP - remote streamable-HTTP at
+    // https://mcp.plaud.ai/mcp. Same Granola/Kajabi/Otter 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). NOT the stdio `npx @plaud-ai/mcp` package,
+    // which runs its own local browser sign-in and token file. Values below
+    // are taken verbatim from the metadata (re-read 2026-10-16), not inferred:
+    //   - https://mcp.plaud.ai/.well-known/oauth-protected-resource (and the
+    //     path-suffixed /.well-known/oauth-protected-resource/mcp the server's
+    //     401 points at) give resource https://mcp.plaud.ai/mcp, AS
+    //     https://mcp.plaud.ai/, bearer in the header;
+    //   - https://mcp.plaud.ai/.well-known/oauth-authorization-server (and
+    //     the identical openid-configuration) give authorize /authorize, token
+    //     /token, register /register, PKCE S256 only, `none` among the token
+    //     auth methods, and the authorization_code + refresh_token grants.
+    // NOT advertised: `scopes_supported` (so defaultScopes is empty, the
+    // notion-cli precedent, and the authorize URL carries `scope=`) and
+    // `revocation_endpoint` (so there is no revokeUrl: disconnecting here
+    // deletes our copy of the token but cannot revoke Plaud's grant; the user
+    // revokes it in their Plaud account).
+    //
+    // DCR (operator step, NOT done as of this commit): POST the registration
+    // body by hand to https://mcp.plaud.ai/register with client_name
+    // `Ninjafy`, token_endpoint_auth_method `none`, grant_types
+    // authorization_code + refresh_token, and BOTH API callbacks in
+    // redirect_uris (https://api.augmented.team/integrations/oauth/callback
+    // and https://api.ninjafy.com/integrations/oauth/callback). Do not use
+    // scripts/dcr-register.ts: it takes a single --redirect-uri. Store the
+    // returned client id as OAUTH_PLAUD_CLIENT_ID; unset, Connect soft-fails
+    // "not configured". Full procedure: docs/runbooks/plaud-dogfood.md.
+    definitionId: "plaud",
+    authorizeUrl: "https://mcp.plaud.ai/authorize",
+    tokenUrl: "https://mcp.plaud.ai/token",
+    defaultScopes: [],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.plaud.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // Plaud advertises NO scopes, so the token is not scope-limited: the
+    // read-only property of this integration rests ENTIRELY on this
+    // allowlist, which the remote-oauth-proxy enforces on tools/list and
+    // tools/call. The five names are Plaud's documented read tools
+    // (https://docs.plaud.ai/plaud-mcp-cli/mcp). `login` and `logout` are
+    // deliberately excluded: sign-in is our OAuth broker's job, and `logout`
+    // revokes the user's authorization, which an agent must never do. The
+    // names come from the docs, not from an authenticated tools/list (that
+    // needs a consented token), and the proxy SKIPS an allowlisted name the
+    // server does not serve, so confirm against the first live tools/list
+    // (runbook Step 3, a gate before customer use).
+    toolAllowlist: ["get_current_user", "list_files", "get_file", "get_note", "get_transcript"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -40212,6 +40267,36 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
     beta: true
   },
+  {
+    id: "plaud",
+    name: "Plaud",
+    category: "knowledge",
+    description: "Read Plaud recordings: list and search recordings by name or date, and read their AI notes (summary, action items, key topics) and full speaker-labelled transcripts.",
+    // ENG-11543 (CS-2134): same remote streamable-HTTP MCP + OAuth pattern as
+    // Granola/Kajabi/Otter, against Plaud's HOSTED server (https://mcp.plaud.ai/mcp),
+    // not the stdio `npx @plaud-ai/mcp` package. Discovery chain: RFC 9728
+    // protected-resource metadata at mcp.plaud.ai -> RFC 8414 AS metadata on the
+    // same host -> RFC 7591 registration at /register. Auth is OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client registered once by
+    // an operator (docs/runbooks/plaud-dogfood.md -> OAUTH_PLAUD_CLIENT_ID).
+    // Consent is brokered through the shared /integrations/oauth/authorize ->
+    // /callback path, and the token reaches the host via the generic
+    // remote-oauth-proxy (OAUTH_PROVIDERS.plaud.mcpUrl).
+    //
+    // READ-ONLY RESTS ENTIRELY ON THE TOOL ALLOWLIST. Unlike Otter, Plaud
+    // advertises NO scopes_supported, so there is no read scope to request and
+    // the granted token is not scope-limited. What keeps this integration
+    // read-only is OAUTH_PROVIDERS.plaud.toolAllowlist (the five documented
+    // reads), which the proxy enforces on tools/list and tools/call. `login` and
+    // `logout` are excluded; `logout` would revoke the user's authorization.
+    // Anything that widens the allowlist widens what the token can do.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "plaud:read", name: "Read Recordings & Transcripts", description: "List and search recordings by name or date, and read their details, AI notes (summary, action items, key topics) and full transcripts with speaker labels (get_current_user, list_files, get_file, get_note, get_transcript)", access: "read" }
+    ],
+    docs_url: "https://docs.plaud.ai/plaud-mcp-cli/mcp",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",

package/dist/mcp/slack-channel.js

@@ -34143,6 +34143,61 @@ var OAUTH_PROVIDERS = {
     // tools/list after a real consent (runbook Step 3).
     toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
   },
+  "plaud": {
+    // ENG-11543 (CS-2134): Plaud's hosted MCP - remote streamable-HTTP at
+    // https://mcp.plaud.ai/mcp. Same Granola/Kajabi/Otter 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). NOT the stdio `npx @plaud-ai/mcp` package,
+    // which runs its own local browser sign-in and token file. Values below
+    // are taken verbatim from the metadata (re-read 2026-10-16), not inferred:
+    //   - https://mcp.plaud.ai/.well-known/oauth-protected-resource (and the
+    //     path-suffixed /.well-known/oauth-protected-resource/mcp the server's
+    //     401 points at) give resource https://mcp.plaud.ai/mcp, AS
+    //     https://mcp.plaud.ai/, bearer in the header;
+    //   - https://mcp.plaud.ai/.well-known/oauth-authorization-server (and
+    //     the identical openid-configuration) give authorize /authorize, token
+    //     /token, register /register, PKCE S256 only, `none` among the token
+    //     auth methods, and the authorization_code + refresh_token grants.
+    // NOT advertised: `scopes_supported` (so defaultScopes is empty, the
+    // notion-cli precedent, and the authorize URL carries `scope=`) and
+    // `revocation_endpoint` (so there is no revokeUrl: disconnecting here
+    // deletes our copy of the token but cannot revoke Plaud's grant; the user
+    // revokes it in their Plaud account).
+    //
+    // DCR (operator step, NOT done as of this commit): POST the registration
+    // body by hand to https://mcp.plaud.ai/register with client_name
+    // `Ninjafy`, token_endpoint_auth_method `none`, grant_types
+    // authorization_code + refresh_token, and BOTH API callbacks in
+    // redirect_uris (https://api.augmented.team/integrations/oauth/callback
+    // and https://api.ninjafy.com/integrations/oauth/callback). Do not use
+    // scripts/dcr-register.ts: it takes a single --redirect-uri. Store the
+    // returned client id as OAUTH_PLAUD_CLIENT_ID; unset, Connect soft-fails
+    // "not configured". Full procedure: docs/runbooks/plaud-dogfood.md.
+    definitionId: "plaud",
+    authorizeUrl: "https://mcp.plaud.ai/authorize",
+    tokenUrl: "https://mcp.plaud.ai/token",
+    defaultScopes: [],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.plaud.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // Plaud advertises NO scopes, so the token is not scope-limited: the
+    // read-only property of this integration rests ENTIRELY on this
+    // allowlist, which the remote-oauth-proxy enforces on tools/list and
+    // tools/call. The five names are Plaud's documented read tools
+    // (https://docs.plaud.ai/plaud-mcp-cli/mcp). `login` and `logout` are
+    // deliberately excluded: sign-in is our OAuth broker's job, and `logout`
+    // revokes the user's authorization, which an agent must never do. The
+    // names come from the docs, not from an authenticated tools/list (that
+    // needs a consented token), and the proxy SKIPS an allowlisted name the
+    // server does not serve, so confirm against the first live tools/list
+    // (runbook Step 3, a gate before customer use).
+    toolAllowlist: ["get_current_user", "list_files", "get_file", "get_note", "get_transcript"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -34599,6 +34654,36 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
     beta: true
   },
+  {
+    id: "plaud",
+    name: "Plaud",
+    category: "knowledge",
+    description: "Read Plaud recordings: list and search recordings by name or date, and read their AI notes (summary, action items, key topics) and full speaker-labelled transcripts.",
+    // ENG-11543 (CS-2134): same remote streamable-HTTP MCP + OAuth pattern as
+    // Granola/Kajabi/Otter, against Plaud's HOSTED server (https://mcp.plaud.ai/mcp),
+    // not the stdio `npx @plaud-ai/mcp` package. Discovery chain: RFC 9728
+    // protected-resource metadata at mcp.plaud.ai -> RFC 8414 AS metadata on the
+    // same host -> RFC 7591 registration at /register. Auth is OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client registered once by
+    // an operator (docs/runbooks/plaud-dogfood.md -> OAUTH_PLAUD_CLIENT_ID).
+    // Consent is brokered through the shared /integrations/oauth/authorize ->
+    // /callback path, and the token reaches the host via the generic
+    // remote-oauth-proxy (OAUTH_PROVIDERS.plaud.mcpUrl).
+    //
+    // READ-ONLY RESTS ENTIRELY ON THE TOOL ALLOWLIST. Unlike Otter, Plaud
+    // advertises NO scopes_supported, so there is no read scope to request and
+    // the granted token is not scope-limited. What keeps this integration
+    // read-only is OAUTH_PROVIDERS.plaud.toolAllowlist (the five documented
+    // reads), which the proxy enforces on tools/list and tools/call. `login` and
+    // `logout` are excluded; `logout` would revoke the user's authorization.
+    // Anything that widens the allowlist widens what the token can do.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "plaud:read", name: "Read Recordings & Transcripts", description: "List and search recordings by name or date, and read their details, AI notes (summary, action items, key topics) and full transcripts with speaker labels (get_current_user, list_files, get_file, get_note, get_transcript)", access: "read" }
+    ],
+    docs_url: "https://docs.plaud.ai/plaud-mcp-cli/mcp",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",

package/dist/mcp/telegram-channel.js

@@ -34377,6 +34377,61 @@ var OAUTH_PROVIDERS = {
     // tools/list after a real consent (runbook Step 3).
     toolAllowlist: ["otter_get_user_info", "otter_search", "otter_fetch"]
   },
+  "plaud": {
+    // ENG-11543 (CS-2134): Plaud's hosted MCP - remote streamable-HTTP at
+    // https://mcp.plaud.ai/mcp. Same Granola/Kajabi/Otter 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). NOT the stdio `npx @plaud-ai/mcp` package,
+    // which runs its own local browser sign-in and token file. Values below
+    // are taken verbatim from the metadata (re-read 2026-10-16), not inferred:
+    //   - https://mcp.plaud.ai/.well-known/oauth-protected-resource (and the
+    //     path-suffixed /.well-known/oauth-protected-resource/mcp the server's
+    //     401 points at) give resource https://mcp.plaud.ai/mcp, AS
+    //     https://mcp.plaud.ai/, bearer in the header;
+    //   - https://mcp.plaud.ai/.well-known/oauth-authorization-server (and
+    //     the identical openid-configuration) give authorize /authorize, token
+    //     /token, register /register, PKCE S256 only, `none` among the token
+    //     auth methods, and the authorization_code + refresh_token grants.
+    // NOT advertised: `scopes_supported` (so defaultScopes is empty, the
+    // notion-cli precedent, and the authorize URL carries `scope=`) and
+    // `revocation_endpoint` (so there is no revokeUrl: disconnecting here
+    // deletes our copy of the token but cannot revoke Plaud's grant; the user
+    // revokes it in their Plaud account).
+    //
+    // DCR (operator step, NOT done as of this commit): POST the registration
+    // body by hand to https://mcp.plaud.ai/register with client_name
+    // `Ninjafy`, token_endpoint_auth_method `none`, grant_types
+    // authorization_code + refresh_token, and BOTH API callbacks in
+    // redirect_uris (https://api.augmented.team/integrations/oauth/callback
+    // and https://api.ninjafy.com/integrations/oauth/callback). Do not use
+    // scripts/dcr-register.ts: it takes a single --redirect-uri. Store the
+    // returned client id as OAUTH_PLAUD_CLIENT_ID; unset, Connect soft-fails
+    // "not configured". Full procedure: docs/runbooks/plaud-dogfood.md.
+    definitionId: "plaud",
+    authorizeUrl: "https://mcp.plaud.ai/authorize",
+    tokenUrl: "https://mcp.plaud.ai/token",
+    defaultScopes: [],
+    supportsRefresh: true,
+    extraAuthorizeParams: {},
+    clientAuthMethod: "body",
+    pkce: "S256",
+    publicClient: true,
+    mcpUrl: "https://mcp.plaud.ai/mcp",
+    // Curated surface (matches the catalog seed's defined_scopes[].tools).
+    // Plaud advertises NO scopes, so the token is not scope-limited: the
+    // read-only property of this integration rests ENTIRELY on this
+    // allowlist, which the remote-oauth-proxy enforces on tools/list and
+    // tools/call. The five names are Plaud's documented read tools
+    // (https://docs.plaud.ai/plaud-mcp-cli/mcp). `login` and `logout` are
+    // deliberately excluded: sign-in is our OAuth broker's job, and `logout`
+    // revokes the user's authorization, which an agent must never do. The
+    // names come from the docs, not from an authenticated tools/list (that
+    // needs a consented token), and the proxy SKIPS an allowlisted name the
+    // server does not serve, so confirm against the first live tools/list
+    // (runbook Step 3, a gate before customer use).
+    toolAllowlist: ["get_current_user", "list_files", "get_file", "get_note", "get_transcript"]
+  },
   "notion-cli": {
     // Notion's public OAuth app. Tokens are workspace-scoped and long-lived —
     // Notion does not issue refresh_tokens, so `supportsRefresh: false` and
@@ -34833,6 +34888,36 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://help.otter.ai/hc/en-us/articles/35287607569687-Otter-MCP-Server",
     beta: true
   },
+  {
+    id: "plaud",
+    name: "Plaud",
+    category: "knowledge",
+    description: "Read Plaud recordings: list and search recordings by name or date, and read their AI notes (summary, action items, key topics) and full speaker-labelled transcripts.",
+    // ENG-11543 (CS-2134): same remote streamable-HTTP MCP + OAuth pattern as
+    // Granola/Kajabi/Otter, against Plaud's HOSTED server (https://mcp.plaud.ai/mcp),
+    // not the stdio `npx @plaud-ai/mcp` package. Discovery chain: RFC 9728
+    // protected-resource metadata at mcp.plaud.ai -> RFC 8414 AS metadata on the
+    // same host -> RFC 7591 registration at /register. Auth is OAuth 2.0
+    // authorization-code with PKCE (S256) and a public client registered once by
+    // an operator (docs/runbooks/plaud-dogfood.md -> OAUTH_PLAUD_CLIENT_ID).
+    // Consent is brokered through the shared /integrations/oauth/authorize ->
+    // /callback path, and the token reaches the host via the generic
+    // remote-oauth-proxy (OAUTH_PROVIDERS.plaud.mcpUrl).
+    //
+    // READ-ONLY RESTS ENTIRELY ON THE TOOL ALLOWLIST. Unlike Otter, Plaud
+    // advertises NO scopes_supported, so there is no read scope to request and
+    // the granted token is not scope-limited. What keeps this integration
+    // read-only is OAUTH_PROVIDERS.plaud.toolAllowlist (the five documented
+    // reads), which the proxy enforces on tools/list and tools/call. `login` and
+    // `logout` are excluded; `logout` would revoke the user's authorization.
+    // Anything that widens the allowlist widens what the token can do.
+    supported_auth_types: ["oauth2"],
+    capabilities: [
+      { id: "plaud:read", name: "Read Recordings & Transcripts", description: "List and search recordings by name or date, and read their details, AI notes (summary, action items, key topics) and full transcripts with speaker labels (get_current_user, list_files, get_file, get_note, get_transcript)", access: "read" }
+    ],
+    docs_url: "https://docs.plaud.ai/plaud-mcp-cli/mcp",
+    beta: true
+  },
   {
     id: "anchor-browser",
     name: "Anchor Browser",

package/dist/{persistent-session-YDKIHRCX.js → persistent-session-WE42P4HU.js}

@@ -68,8 +68,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-TRZ4SG77.js";
-import "./chunk-KN4GAY5Z.js";
+} from "./chunk-LIWZ3QER.js";
+import "./chunk-CA4OFLW4.js";
 import "./chunk-B6UYVEMD.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -145,4 +145,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-YDKIHRCX.js.map
+//# sourceMappingURL=persistent-session-WE42P4HU.js.map

package/dist/{responsiveness-probe-5LEQ4ZFE.js → responsiveness-probe-6AG6PYW7.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-TRZ4SG77.js";
-import "./chunk-KN4GAY5Z.js";
+} from "./chunk-LIWZ3QER.js";
+import "./chunk-CA4OFLW4.js";
 import "./chunk-B6UYVEMD.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -802,4 +802,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-5LEQ4ZFE.js.map
+//# sourceMappingURL=responsiveness-probe-6AG6PYW7.js.map

package/dist/{session-auth-dead-C3GYATAO.js → session-auth-dead-H7UDGEIS.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-KN4GAY5Z.js";
+} from "./chunk-CA4OFLW4.js";
 import "./chunk-DGUM43GV.js";
 
 // src/lib/session-auth-dead.ts
@@ -204,4 +204,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-C3GYATAO.js.map
+//# sourceMappingURL=session-auth-dead-H7UDGEIS.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.1130",
+  "version": "0.28.1132",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {