Replicate's official MCP server: search thousands of hosted models, read their schemas, and run predictions on image, video, audio and language models from inside an agent.
Summary
1Password's official local MCP server for dev secrets: the agent manages Environments and .env mounts by name, and never sees a secret value.
Features
- Seven tools for creating, listing and renaming Environments and their variables
- Never returns secret values — the model sees Environment and variable names only
- Creates locally mounted .env files so secrets reach a process without being written to disk
- Works with op:// secret references resolved at execution time by `op run`
- stdio transport; requires the 1Password desktop app and an active account
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
Agent configurations are where credentials go to leak — pasted into a .env, committed to a repo, or handed to a model in plain text. 1Password's Environments MCP server is built so that cannot happen: the server exposes the names of Environments and variables, and never returns the stored secret values, which stay in 1Password.
What the agent can do
Seven tools, split between read and write:
| Tool | Purpose |
| --- | --- |
| authenticate | Authenticate against the 1Password desktop app |
| list_environments | List Environments (read-only) |
| list_variables | List variable names in an Environment (read-only) |
| create_environment | Create a new Environment |
| rename_environment | Rename an existing Environment |
| append_variables | Add or update variables |
| create_local_env_file | Create a locally mounted .env file |
The mounted .env is the mechanism that makes this useful rather than merely safe: secrets become available to a process on demand without ever being written to disk in the clear, and op run resolves op:// references in memory for the life of the process.
Requirements
An active 1Password account, the 1Password desktop app installed, at least one Environment created, and an MCP client that supports stdio transport — remote-only clients cannot use this server. Cursor and Kiro plugins are in beta.
Who it is for
Developers running coding agents that need real credentials to run or test code, in teams where handing those credentials to a model — or to a config file in the repo — is not acceptable.
Related MCP Servers
Hugging Face's official remote MCP server — search and inspect models, datasets and Spaces, browse the Hub filesystem over hf:// URIs, and turn Gradio Spaces into callable tools.
Resend's official MCP server for transactional and marketing email — send, schedule and batch messages, manage templates, contacts, broadcasts, automations, domains and suppressions from an agent.
1 views
Postman's official MCP server — reach your workspaces, collections, specs and environments from Claude Code, Cursor, VS Code or Copilot, in four tool tiers.
3 views