maisecrets / With mcpgate
maisecrets and mcpgate, together
mcpgate is the gateway between your AI and your company's tools: it pseudonymizes personal data in their results. maisecrets runs on your computer and guards what never passes the gateway. Vault references join the two.
c in its key (SECRET_c1) is maisecrets’ own, kept in your local vault; a token without it (EMAIL_1) is mcpgate’s, kept in the gateway.Who protects what
| The value | Where it goes | Who protects it |
|---|---|---|
A password you type, a key in .env, a token in command output | stays on your computer | maisecrets: the model gets a placeholder, your command the real value |
| A customer’s address in a Jira ticket or a CRM record | comes from a company tool | mcpgate: the model gets a token |
| That address in a reply the AI posts back to the tool | goes to a company tool | mcpgate puts the real value into the call |
| That address in a letter the AI writes into a local file | goes to your disk | maisecrets asks mcpgate for the value (Sensitive Reference in Claude Code, or vault reference) |
Why both
A gateway protects what goes through it. We counted our own Claude Code sessions: 185 real credentials across 3,254 sessions, and 80% of them never passed the gateway. They came from files and commands on the laptop. maisecrets covers that part, and vault references let a local file get a value that only mcpgate knows.
Each one works alone. maisecrets is free and does not need mcpgate. mcpgate does not need maisecrets.
Set it up
- Run mcpgate and connect your tools.
- Install maisecrets in Claude Code or Codex.
- For vault references, the operator of mcpgate turns on “Let local vaults read values”. The steps and the states: Vault references. The protocol: Local vaults.
- For Sensitive References, the administrator of your gateway turns them on for an allow list of users, and each user approves a program each time it signs in. The feature is experimental.