Answer: An MCP server's environment can name a stored secret as secret://NAME, and the value is resolved from the vault at spawn time so the secret never sits in on-disk config. If the named secret is missing from the vault, the spawn fails rather than starting the server without it. Status: Confirmed Entry: tool/kiro/permissions-and-security/secrets-vault-mcp Revision: 1 Digest: sha256:eb0447da5d0b7420 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:34Z Last changed: 2026-11-13T03:39:34Z Last verified: 2026-11-20T13:24:32Z Next check: 2026-11-21T13:24:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of secret reference syntax | secret://NAME | [1] | 2026-11-20 resolution timing | at spawn time | [1] | 2026-11-20 example env value | secret://EXAMPLE_API_TOKEN | [1] | 2026-11-20 missing secret behavior | the spawn fails | [1] | 2026-11-20 vault management location | Settings → Secrets | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Security - Crew - Docs - Kiro". https://kiro.dev/docs/crew/security/ Role: primary. Accessed: 2026-11-20T13:24:32Z Quote: "An MCP server's environment can name a stored secret as secret://NAME ." (Supports: secret reference syntax) Quote: "The value is resolved from the vault at spawn time, so the secret never sits in on-disk config" (Supports: resolution timing) Quote: ""API_TOKEN" : "secret://EXAMPLE_API_TOKEN"" (Supports: example env value) Quote: "If the named secret is missing from the vault, the spawn fails rather than starting the server without it." (Supports: missing secret behavior) Quote: "Manage them from Settings → Secrets in the dashboard" (Supports: vault management location) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 5c56be3e27af4e916210ea90f4a1eefe3057bb005c0fdc083e77eca01a93341e (captured 2026-11-20T13:24:32Z) 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:24:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:32Z Last attempt: 2026-11-20T13:24:32Z Notes and limitations: Extracted automatically from a single official source (section "Secrets vault"). Related: https://latestn.com/tool/kiro/permissions-and-security/security-pre-commit-scanner-hook How do I set up a Kiro hook that scans for security issues before a commit? https://latestn.com/tool/kiro/permissions-and-security/slack-tool-approval How do I enable interactive tool approval for Kiro Crew in Slack? https://latestn.com/tool/kiro/permissions-and-security/supervised-mode What does Supervised mode do in Kiro and when should I use it? https://latestn.com/tool/kiro/permissions-and-security/sandbox-platform-requirements What platforms does the Kiro local command sandbox require? https://latestn.com/tool/kiro/permissions-and-security/sandbox-secrets How do I add secrets to a Kiro web sandbox? https://latestn.com/tool/kiro/permissions-and-security/sandbox-stdio-mcp-servers How do I sandbox stdio MCP servers in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:39:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/secrets-vault-mcp/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/permissions-and-security/secrets-vault-mcp POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/secrets-vault-mcp with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/secrets-vault-mcp?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I store and reference secrets from an MCP server in Kiro Crew's secrets vault? Revision 1, last verified 2026-11-20T13:24:32Z. https://latestn.com/tool/kiro/permissions-and-security/secrets-vault-mcp (accessed 2026-11-21T10:07:47Z). @misc{LatestN_tool_kiro_permissions_and_security_secrets_vault_mcp_r1, title = {How do I store and reference secrets from an MCP server in Kiro Crew's secrets vault?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/secrets-vault-mcp}}, note = {Revision 1; digest sha256:eb0447da5d0b7420; last verified 2026-11-20T13:24:32Z; accessed 2026-11-21T10:07:47Z} } 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/permissions-and-security/secrets-vault-mcp