1Claw Vault vs Emilia Protocol
A side-by-side look at the 1Claw Vault and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 1Claw Vault for security work as a local process; choose Emilia Protocol for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 1Claw Vault when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ONECLAW_AGENT_API_KEY, ONECLAW_AGENT_TOKEN, ONECLAW_VAULT_ID, ONECLAW_LOCAL_ONLY, ONECLAW_LOCAL_VAULT, ONECLAW_DAEMON_SOCKET, MCP_TRANSPORT, PORT. - You want tools like
list_secrets, get_secret, put_secret.
Choose Emilia Protocol when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ep_guard_action, ep_check_signoff, ep_verify_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 56/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | ONECLAW_AGENT_API_KEY |
Tools & capabilities
1Claw Vault tools 37
list_secretsList all secrets (metadata only — never values)get_secretFetch the decrypted value of a secret by path. Accepts optional `client_share` for MPC vaults.put_secretCreate or update a secret (creates a new version). Response includes `client_share` when the vault has MPC enabled.delete_secretSoft-delete a secret at a pathdescribe_secretGet metadata without fetching the valuerotate_and_storeStore a new value for an existing secret and return the versionrotate_generateServer-side secret rotation with generated value (length, charset configurable)list_versionsList all versions of a secret (version numbers, dates, disabled status)get_env_bundleFetch an env_bundle secret and parse it as KEY=VALUE JSONlist_child_agentsChild agents under a parent (own key/memory/policy, subset of the parent's access; vault ≥ 0.61.30)resolve_envResolve environment variables for a vault and environment (returns the final KEY=VALUE set with precedence applied). When the agent has `env_auto_resolve: true`, omit `environment` and the server uses the agent's tagged environment from the JWT.create_vaultCreate a new vault (auto-shared with the agent's human creator)- +25 more on the listing page
Emilia Protocol tools 3
ep_guard_actionRequest authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
1Claw Vault
{
"mcpServers": {
"1claw-vault": {
"command": "npx",
"args": [
"-y",
"@1claw/mcp"
],
"env": {
"ONECLAW_AGENT_API_KEY": "YOUR_ONECLAW_AGENT_API_KEY_HERE",
"ONECLAW_AGENT_TOKEN": "YOUR_ONECLAW_AGENT_TOKEN_HERE",
"ONECLAW_VAULT_ID": "YOUR_ONECLAW_VAULT_ID_HERE",
"ONECLAW_LOCAL_ONLY": "YOUR_ONECLAW_LOCAL_ONLY_HERE",
"ONECLAW_LOCAL_VAULT": "YOUR_ONECLAW_LOCAL_VAULT_HERE",
"ONECLAW_DAEMON_SOCKET": "YOUR_ONECLAW_DAEMON_SOCKET_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Frequently asked questions
1Claw Vault is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick 1Claw Vault for security work and Emilia Protocol for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
1Claw Vault has no declared pricing — check the project's own site. Auth: api key required. Emilia Protocol is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add 1claw-vault and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 1Claw Vault has a quality signal of 56/100 (Good) with 4 views, 0 installs and 2 GitHub stars. Emilia Protocol has 71/100 (Great) with 5 views, 0 installs and 612 GitHub stars.
