Terminal
Terminal/Skill
Lets your agent set up 1Password Environments and local .env files for a repo, listing variable names without revealing secret values.
By 1Password
Works with
npx skills add 1password/1password-codex-plugin --skill 1password-environmentsUse the local 1Password MCP server for all environment variable configuration. Its tools return variable names, never secret values, so secrets stay in 1Password.
.env files from 1Password..env file from a secret manager and 1Password is available.Do not use this skill for unrelated password-manager tasks, arbitrary local .env file parsing, or non-1Password secret stores unless the user asks to migrate that configuration into 1Password.
This skill depends on the local 1Password MCP server. If its tools are not available in the current session, help the user finish setup instead of improvising:
Install the 1Password desktop app and enable the MCP server in Settings > Developer. On business accounts, the setting is unavailable until an administrator enables the feature in the "Sharing & Permissions" policies section of the admin dashboard.
The desktop app installs the 1password-mcp alias on the PATH (supported on macOS, Windows, and Linux).
Configure the client to launch 1password-mcp as a local MCP server. For Codex, add this to ~/.codex/config.toml:
[mcp_servers.1password]
command = "1password-mcp"
The 1Password desktop app asks the user to approve each client connection, and environment access can require additional approval.
The local server exposes these tools:
authenticate: authenticate with the 1Password desktop app and return the account ID.list_environments: list Developer Environments for an account.create_environment: create a new Developer Environment.rename_environment: rename an existing Developer Environment.list_variables: list variable names in an Environment without returning values.append_variables: add or update Environment variables.create_local_env_file: mount an Environment as a local .env file on macOS or Linux.list_local_env_files: list local .env mounts for an Environment.It also exposes these documentation resources:
1password://docs/getting-started1password://docs/environments-guideauthenticate first when you do not already have an account ID for this turn. The 1Password desktop app will ask the user to approve the connection.accountId for subsequent calls. Server docs may spell the returned value as account_id; MCP tool calls use camelCase parameters such as accountId and environmentId.list_environments with the returned accountId before operating on an Environment, unless the user already provided a current environmentId.environmentId returned by the server for environment-level calls.list_variables when the user wants to inspect an Environment. It returns names only, not secret values.append_variables only when the user explicitly asks to add or update variables.create_local_env_file for local .env mounts on macOS or Linux, and pass the absolute mountPath the user wants.list_local_env_files to check existing local mounts before creating a duplicate..envauthenticate.list_environments.list_local_env_files for the selected Environment to avoid duplicate mounts..env path as mountPath.create_local_env_file with accountId, environmentId, environmentName, and the absolute mountPath..env file to verify it.authenticate.list_environments unless the user already gave an environmentId.environmentId returned by the server for environment-level calls.list_variables and summarize variable names only.authenticate and resolve the target Environment.list_variables first so you can tell whether the requested variable names already exist.append_variables using the active MCP tool schema exactly as exposed in the current session.{ "name": "API_KEY", "value": "...", "concealed": true } for secrets and concealed: false only for non-sensitive values such as URLs or feature flags.variables as string[], do not send unsupported object fields. Use the string format required by that schema, and ask for clarification if the user's requested variable format is ambiguous..env mounts are documented for macOS and Linux only..env file just to verify it exists; use the MCP tools instead..env mounts as sensitive even though 1Password does not persist plaintext secret contents to disk.