Answer: Add an oauth object to the remote server's entry in mcpServers with properties such as clientId, clientSecret, redirectUri, and oauthScopes; Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. Status: Confirmed Entry: tool/kiro/integrations/mcp-oauth-authentication Revision: 5 Digest: sha256:03c8d48f1ab520e9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:43:21Z Last changed: 2026-11-20T13:30:22Z (clientSecret behavior: — → Only meaningful alongside clientId .) Last verified: 2026-11-20T13:30:22Z Next check: 2026-11-21T13:30:22Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of OAuth handling | Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. | [1] | 2026-11-20 Example clientId | your-client-id | [1] | 2026-11-20 Example redirectUri | http://127.0.0.1:8080/oauth/callback | [1] | 2026-11-20 Example oauthScopes | [ "read" , "write" ] | [1] | 2026-11-20 DCR default | Most servers use Dynamic Client Registration (DCR) and need no extra configuration - just connect, and Kiro opens the authorization page. | [1] | 2026-11-20 clientId behavior | When set, Dynamic Client Registration is skipped entirely. | [1] | 2026-11-20 clientSecret behavior | Only meaningful alongside clientId . | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Configuration - MCP - Features - Docs - Kiro". https://kiro.dev/docs/mcp/configuration/ Role: primary. Accessed: 2026-11-20T13:30:22Z Quote: "Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server." (Supports: OAuth handling) Quote: ""clientId" : "your-client-id"" (Supports: Example clientId) Quote: ""redirectUri" : "http://127.0.0.1:8080/oauth/callback"" (Supports: Example redirectUri) Quote: ""oauthScopes" : [ "read" , "write" ]" (Supports: Example oauthScopes) Quote: "Most servers use Dynamic Client Registration (DCR) and need no extra configuration - just connect, and Kiro opens the authorization page." (Supports: DCR default) Quote: "When set, Dynamic Client Registration is skipped entirely." (Supports: clientId behavior) Quote: "Only meaningful alongside clientId ." (Supports: clientSecret behavior) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: bf50318547155b0a22acc10109691e9e2c32b054195a07f1962b2923d4280443 (captured 2026-11-20T13:30:22Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:30:22Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:30:22Z Last attempt: 2026-11-20T13:30:22Z Notes and limitations: Extracted automatically from a single official source (section "OAuth authentication"). Related: https://latestn.com/tool/kiro/integrations/mcp-server-config How do I configure an MCP server in Kiro's agent config? https://latestn.com/tool/kiro/integrations/mcp-servers-multi-root How are MCP servers configured in Kiro multi-root workspaces? https://latestn.com/tool/kiro/integrations/mcp-servers-not-in-registry How do I use an MCP server in Kiro that isn't in the registry? https://latestn.com/tool/kiro/integrations/mcp-auth-slash-command How do I manage MCP server authentication in Kiro with slash commands? https://latestn.com/tool/kiro/integrations/mcp-config-file-locations Where does Kiro look for MCP configuration files and how do I create one? https://latestn.com/tool/kiro/integrations/mcp-install-link-schema What is the schema for a Kiro MCP server install link? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:30:22Z | changed | clientSecret behavior: — → Only meaningful alongside clientId . | [1] 2026-11-20T13:30:22Z | changed | clientId behavior: — → When set, Dynamic Client Registration is skipped entirely. | [1] 2026-11-20T13:30:22Z | changed | DCR default: — → Most servers use Dynamic Client Registration (DCR) and need no extra configuration - just connect, and Kiro opens the authorization page. | [1] 2026-11-20T13:30:22Z | changed | Example oauthScopes: — → [ "read" , "write" ] | [1] 2026-11-20T13:30:22Z | changed | Example redirectUri: — → http://127.0.0.1:8080/oauth/callback | [1] 2026-11-20T13:30:22Z | changed | Example clientId: — → your-client-id | [1] 2026-11-20T13:30:22Z | changed | OAuth handling: — → Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. | [1] 2026-11-20T13:30:22Z | changed | Example redirect URI: http://localhost:7778/oauth/callback → — | [1] 2026-11-20T13:30:22Z | changed | Default behavior: Dynamic Client Registration → — | [1] 2026-11-20T13:30:22Z | changed | oauthScopes property: oauth.oauthScopes → — | [1] 2026-11-20T13:30:22Z | changed | clientMetadataUrl property: oauth.clientMetadataUrl → — | [1] 2026-11-20T13:30:22Z | changed | redirectUri property: oauth.redirectUri → — | [1] 2026-11-20T13:30:22Z | changed | clientSecret property: oauth.clientSecret → — | [1] 2026-11-20T13:30:22Z | changed | clientId property: oauth.clientId → — | [1] 2026-11-20T13:30:22Z | changed | OAuth config object: "oauth" → — | [1] 2026-11-18T13:25:14Z | changed | Example redirect URI: — → http://localhost:7778/oauth/callback | [1] 2026-11-18T13:25:14Z | changed | Default behavior: — → Dynamic Client Registration | [1] 2026-11-18T13:25:14Z | changed | clientMetadataUrl property: — → oauth.clientMetadataUrl | [1] 2026-11-18T13:25:14Z | changed | OAuth config object: — → "oauth" | [1] 2026-11-18T13:25:14Z | changed | default scopes: openid , email , profile , offline_access → — | [1] 2026-11-18T13:25:14Z | changed | oauthScopes property: OAuth scopes to request from the authorization server. → oauth.oauthScopes | [1] 2026-11-18T13:25:14Z | changed | redirectUri property: Custom loopback redirect URI for the OAuth callback. → oauth.redirectUri | [1] 2026-11-18T13:25:14Z | changed | clientSecret property: Client secret for servers that require one. Only meaningful alongside clientId . → oauth.clientSecret | [1] 2026-11-18T13:25:14Z | changed | clientId property: Pre-registered OAuth client ID. When set, Dynamic Client Registration is skipped entirely. → oauth.clientId | [1] 2026-11-18T13:25:14Z | changed | automatic flow: Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. → — | [1] 2026-11-18T13:25:14Z | changed | oauth object: "oauth" : { "clientId" : "your-client-id" , "redirectUri" : "http://127.0.0.1:8080/oauth/callback" , "oauthScopes" : [ "read" , "write" ] } → — | [1] 2026-11-17T13:53:03Z | changed | default scopes: — → openid , email , profile , offline_access | [1] 2026-11-17T13:53:03Z | changed | automatic flow: — → Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. | [1] 2026-11-17T13:53:03Z | changed | oauth object: — → "oauth" : { "clientId" : "your-client-id" , "redirectUri" : "http://127.0.0.1:8080/oauth/callback" , "oauthScopes" : [ "read" , "write" ] } | [1] 2026-11-17T13:53:03Z | changed | Default scopes: openid , email , profile , offline_access → — | [1] 2026-11-17T13:53:03Z | changed | oauthScopes property: OAuth scopes to request from the authorization server. Takes priority over top-level oauthScopes . → OAuth scopes to request from the authorization server. | [1] 2026-11-17T13:53:03Z | changed | DCR default: Most servers use Dynamic Client Registration (DCR) and need no extra configuration → — | [1] 2026-11-17T13:53:03Z | changed | Automatic flow: Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. → — | [1] 2026-11-17T13:53:03Z | changed | OAuth object example: "oauth" : { "clientId" : "your-client-id" , "redirectUri" : "http://127.0.0.1:8080/oauth/callback" , "oauthScopes" : [ "read" , "write" ] } → — | [1] 2026-11-14T13:27:57Z | changed | Default scopes: — → openid , email , profile , offline_access | [1] 2026-11-14T13:27:57Z | changed | oauthScopes property: — → OAuth scopes to request from the authorization server. Takes priority over top-level oauthScopes . | [1] 2026-11-14T13:27:57Z | changed | redirectUri property: — → Custom loopback redirect URI for the OAuth callback. | [1] 2026-11-14T13:27:57Z | changed | clientSecret property: — → Client secret for servers that require one. Only meaningful alongside clientId . | [1] 2026-11-14T13:27:57Z | changed | clientId property: — → Pre-registered OAuth client ID. When set, Dynamic Client Registration is skipped entirely. | [1] 2026-11-14T13:27:57Z | changed | DCR default: — → Most servers use Dynamic Client Registration (DCR) and need no extra configuration | [1] 2026-11-14T13:27:57Z | changed | Automatic flow: — → Kiro handles the browser-based OAuth flow automatically when connecting to an OAuth-protected server. | [1] 2026-11-14T13:27:57Z | changed | OAuth object example: — → "oauth" : { "clientId" : "your-client-id" , "redirectUri" : "http://127.0.0.1:8080/oauth/callback" , "oauthScopes" : [ "read" , "write" ] } | [1] 2026-11-14T13:27:57Z | changed | Kiro hosted metadata URL: https://kiro.dev/oauth/client-metadata.json → — | [1] 2026-11-14T13:27:57Z | changed | IDE client support: The IDE supports public OAuth clients only (PKCE without a client secret) → — | [1] 2026-11-14T13:27:57Z | changed | Client secret support: The CLI supports confidential clients ( clientId + clientSecret ) → — | [1] 2026-11-14T13:27:57Z | changed | DCR behavior: Most servers use Dynamic Client Registration (DCR) and need no extra configuration → — | [1] 2026-11-14T13:27:57Z | changed | Default scopes when none specified: openid , email , profile , offline_access → — | [1] 2026-11-14T13:27:57Z | changed | Example OAuth scopes: oauthScopes → — | [1] 2026-11-14T13:27:57Z | changed | Example redirect URI: http://127.0.0.1:8080/oauth/callback → — | [1] 2026-11-14T13:27:57Z | changed | OAuth object properties: oauth.clientId → — | [1] 2026-11-13T03:43:21Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/integrations/mcp-oauth-authentication/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/integrations/mcp-oauth-authentication POST: https://latestn.com/dispute/tool/kiro/integrations/mcp-oauth-authentication with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/integrations/mcp-oauth-authentication?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure OAuth authentication for a remote MCP server in Kiro? Revision 5, last verified 2026-11-20T13:30:22Z. https://latestn.com/tool/kiro/integrations/mcp-oauth-authentication (accessed 2026-11-21T09:58:02Z). @misc{LatestN_tool_kiro_integrations_mcp_oauth_authentication_r5, title = {How do I configure OAuth authentication for a remote MCP server in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/integrations/mcp-oauth-authentication}}, note = {Revision 5; digest sha256:03c8d48f1ab520e9; last verified 2026-11-20T13:30:22Z; accessed 2026-11-21T09:58:02Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/integrations/mcp-oauth-authentication