1Claw Vault vs PaperPorter — MCP Server Comparison | AllMCPs
1Claw Vault vs PaperPorter
A side-by-side look at the 1Claw Vault and PaperPorter 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 PaperPorter for developer tools. 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.
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 path
describe_secretGet metadata without fetching the value
rotate_and_storeStore a new value for an existing secret and return the version
rotate_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 JSON
list_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)
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for PaperPorter yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
1Claw Vault is categorized under Security and uses a local stdio subprocess. PaperPorter belongs to Developer Tools and uses an install path we have not confirmed yet. Pick 1Claw Vault for security work and PaperPorter for developer tools.
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. PaperPorter has no confirmed install command yet — follow its own setup instructions.
1Claw Vault has no declared pricing — check the project's own site. Auth: api key required. PaperPorter has no declared pricing — check the project's own site. 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 paperporter 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. PaperPorter has 29/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.