# CipherGate MCP server

> A self-hosted secrets manager that provides an MCP interface and a proxy to securely inject credentials into AI agents without exposing them.

- Repository: https://github.com/maverick0628/ciphergate
- Page: https://hostedmcp.org/servers/maverick0628/ciphergate
- Transport: —
- Stars: 2
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `GATEWAY_DB_PATH` | no | no |  |

## FAQ

### How does CipherGate protect secrets from AI agents?

It uses a proxy that injects credentials at runtime and can enforce policies like tool allowlists, argument filtering, and response redaction.

### Can the browser UI show my plaintext secrets?

No, the UI is designed to never display plaintext secrets; it only shows masked versions to prevent accidental exposure or theft.

### Is CipherGate a high-availability solution?

No, it is a single-node store designed for a single node you control, without HA, clustering, or dynamic secrets.

### What happens if I lose my keyfile?

The keyfile is the root of trust; anyone who can read it can read every secret, so it must be protected and backed up separately from the database.
