Authbox

What MARUCIE/authbox MCP server does

MARUCIE/authbox MCP server connects AI agents to an Auth Box credential vault through the Model Context Protocol. It is designed for delegated access rather than direct exposure of the complete vault. Auth Box supports stored credentials, deterministic passwords derived from a seed phrase and site name, and API key management for more than 70 providers.

The gateway is part of a broader zero-knowledge password manager. A 24-word BIP-39 seed phrase is the recovery mechanism, and keys derived from it protect vault data, synchronization, agent delegation, authentication, and deterministic password generation. The product also supports importing credentials from 13 listed password-manager and browser sources, plus automatic .env importing.

How it works

The client holds the cryptographic keys. The server handles encrypted blobs, authentication, vault operations, agent policies, and audit data, but is described as unable to decrypt the vault. The MCP gateway uses WebSocket transport, according to the repository architecture.

Agent access is policy-gated. Policies can restrict the scope of access, limit request frequency, permit access only during defined time windows, and require step-up approval for sensitive actions. Operations are recorded in a hash-chain audit trail, providing a tamper-evident sequence of audit records as described by the project.

MARUCIE/authbox MCP server can operate alongside the optional Auth Box server infrastructure. The README also describes an offline mode in which the vault remains usable with keys derived from the seed phrase, without depending on the server.

Setup and configuration

The repository is a Go, Next.js, and TypeScript monorepo. The documented development setup begins with installing dependencies:

pnpm install

The available development commands are:

make dev
make dev-api
make dev-full

These commands start the web application, the Go API, or the full development environment. The README lists PostgreSQL and Redis as part of the infrastructure started by the development workflow. The web application is available at http://localhost:3010, and the API at http://localhost:4010.

The supplied material does not document a standalone package command, MCP client configuration snippet, required environment variables, or a dedicated production launch command for the gateway. Deployment details therefore require consulting the repository directly.

Tools and capabilities

The available material describes capabilities rather than naming individual MCP tool methods. Supported areas include:

• Delegating credential access to AI agents through MCP.
• Applying scopes, rate limits, time windows, and step-up approval to agent access.
• Maintaining a hash-chain audit trail for access activity.
• Managing passwords and API keys, including keys for more than 70 providers.
• Deriving passwords deterministically from the seed phrase and site name.
• Recovering the vault from a 24-word seed phrase.

MARUCIE/authbox MCP server is therefore most relevant when an agent needs narrowly controlled access to secrets and the operator needs policy and audit controls around that access.

Limitations and notes

The README does not list the exact MCP methods, resource names, request schemas, or supported MCP client applications. It also does not state whether a particular desktop or editor client has been tested. The MCP gateway is described as part of the Auth Box monorepo rather than as a separately published package.

The server-side design is not equivalent to plaintext secret storage: the architecture states that the server stores encrypted blobs only. Losing the seed phrase is consequently significant because it is described as the sole recovery mechanism. Arweave backup is listed as an optional encrypted-vault archive path, but the provided material does not specify its operational setup or costs.