Skip to main content
Glama
CakeRepository

1Password MCP Server

op_run

Run shell commands with 1Password secrets injected as environment variables, keeping sensitive values out of logs and responses. Securely use secrets in scripts and API calls.

Instructions

Run a local shell command with 1Password secrets injected as environment variables — plaintext secret values are NEVER returned to the caller or written to any log; every resolved secret value is redacted from stdout/stderr before the result is returned. This is the safe way to USE a secret in a command, API call, or script: prefer op_run with op://vault/item/field references in env over reading a secret with password_read/item_get and pasting it into a command yourself, which would put the plaintext in the model context and transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory to run the command in, e.g. a repo checkout path.
envNoMap of ENV_VAR_NAME -> value. A value matching op://vault/item/field is resolved via 1Password and injected as plaintext into the child process env only; any other value is passed through unchanged as a literal.
argvNoArgument vector [executable, ...args] to execute directly without a shell (safer against quoting/injection issues). Provide either `command` or `argv`, not both.
shellNoOptional shell executable to use with `command` (e.g. 'powershell.exe', 'C:/Program Files/Git/bin/bash.exe', '/bin/bash'). Defaults to the platform shell (cmd.exe on Windows, /bin/sh elsewhere). Ignored when `argv` is used.
stdinNoOptional text to write to the process's stdin.
commandNoShell command line to execute (run via the platform shell). Provide either `command` or `argv`, not both.
timeout_msNoKill the process if it runs longer than this many milliseconds. Default 120000 (2 minutes).
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully owns behavioral disclosure. It states that plaintext secret values are NEVER returned or logged, that every resolved secret is redacted from stdout/stderr, and that injection occurs only in the child process env. These are critical safety behaviors disclosed beyond what the schema provides. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, but they are dense and packed with purpose, safety, and usage guidance. Every clause adds value, though the length is slightly above minimal. It remains well-structured and front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter command runner with no output schema, the description covers purpose, safety, and usage well. It does not explicitly describe the return format or error behavior, but these are not essential for tool selection/invocation. The safety context and usage alternatives make it sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed per-parameter descriptions (e.g., env explains the op:// resolution and pass-through behavior). The description adds high-level context about env/redaction but doesn't enrich parameter meanings beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Run a local shell command with 1Password secrets injected as environment variables', naming the action and resource, and distinguishes itself from sibling secret-reading tools by explicitly recommending op_run over password_read/item_get for using secrets. This is a specific verb+resource with strong sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool: 'This is the safe way to USE a secret in a command, API call, or script: prefer op_run... over reading a secret with password_read/item_get and pasting it into a command yourself'. It also provides a clear rationale (prevents plaintext in model context/transcript) and names the alternatives, giving complete usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CakeRepository/1Password-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server