# 1Password + Kiro: Trusted Access for AI-Powered Development

DevFeed: [1Password + Kiro: Trusted Access for AI-Powered Development](<https://devfeed.tech/articles/1password-kiro-trusted-access-for-ai-powered-development-1883.md>)

Original publisher: [Read original article](<https://1password.com/blog/1password-kiro-trusted-access>)

Author: info@1password.com (Dennis Kromhout van der Meer and Scott Lougheed)

Published: 2026-06-17T00:00:00Z

Content type: article

Language: en

Sources: [Blog on 1Password Blog](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [coding](<https://devfeed.tech/tags/coding.md>), [developers](<https://devfeed.tech/tags/developers.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [secrets](<https://devfeed.tech/tags/secrets.md>)

## AI overview

1Password announces an integration between its MCP Server and Kiro that gives AI development workflows scoped, runtime credentials without exposing raw secrets in the model context.

## Source excerpt

AI agents now write code, fix bugs, and ship to production. But in order to do useful work, agents require credentials. At 1Password, one of our core AI security principles is that raw credentials should never be directly exposed to LLMs, but all too often, that's exactly what happens: most teams sacrifice security for speed and hand agents secrets in plaintext. The shortcuts behind that tradeoff predate agentic development: secrets packed into an .env file, a script with hardcoded keys, a config file committed to a repo. But agentic development exponentially increases the blast radius of an exposed or misused credential, since anything in an agent's context window can be logged, echoed into output, or surfaced by an agent that's been manipulated into revealing it. Solving this tension means giving agents the access they need without directly exposing credentials to the model context. Today we're expanding the 1Password MCP Server to Kiro, making 1Password the trusted access layer for AI-powered development in Kiro. With this integration, credentials are issued at runtime, scoped to the assigned task, and never enter the model's context window. Agents get the access they need, and secrets stay where they belong. What this integration does Kiro is a software development agent, available in IDE, CLI or web experiences, bringing engineering rigor to AI-native coding via spec driven development and property-based testing. This integration connects Kiro directly to 1Password Environments using a local MCP server packaged inside our Password Manager developer tools. It's available on 1Password business and personal accounts. With this integration, developers can: Configure environments securely inside Kiro. Ask Kiro to create and configure an environment, then run applications using secrets stored in 1Password Environments instead of plaintext .env files, all without leaving Kiro. Clean up hard-coded secrets. Have Kiro find credentials in source code, move them into 1Pass