sync-env-from-1password

Sync Environment Variables from 1Password

Sync environment variables from 1Password to local .env file using environment variable mappings stored in the truth layer (per neotoma_parquet_migration_rules.mdc).

Command

sync_env_from_1password

or

sync env from 1password

Purpose

This command syncs environment variables from 1Password to your local .env file based on mappings stored in the truth layer (per neotoma_parquet_migration_rules.mdc). Parquet path when used: $DATA_DIR/env_var_mappings/env_var_mappings.parquet.

Key features:

• Automatic backup before modification
• Preserves unmanaged environment variables
• Never prints secret values
• Supports environment-based keys (e.g., different API keys for dev/prod)
• Uses 1Password MCP server (preferred) or CLI (fallback)

Prerequisites

Option 1: 1Password MCP Server (Recommended)

Benefits:

• Persistent connection (no session expiration)
• Better error handling
• No repeated authentication
• Consistent with other MCP integrations

Setup:

1. Ensure 1Password CLI is installed:

   brew install 1password-cli
   op signin
   

2. Configure MCP server in ~/.cursor/mcp.json:

   {
     "mcpServers": {
       "onepassword": {
         "command": "bash",
         "args": [
           "/Users/markmhendrickson/repos/ateles/mcp/onepassword/run-onepassword-mcp.sh"
         ],
         "env": {}
       }
     }
   }
   

3. Verify MCP server is running:

   • Restart Cursor after updating mcp.json
   • MCP server status visible in Cursor MCP panel

For detailed setup instructions, see: mcp/onepassword/README.md

Option 2: 1Password CLI (Fallback)

When to use:

• MCP server not configured
• Temporary/one-off sync
• Troubleshooting MCP issues

Setup:

1. Install 1Password CLI:

   brew install 1password-cli
   

2. Sign in:

   op signin
   

Note: CLI sessions expire periodically and require re-authentication.