Plugins
Secrets
Store, rotate and export encrypted credentials.
Vault
Secrets is your password manager, everything in one list: logins (username, password, websites, one-time code), secure notes and cards, plus custom fields, tags and favorites. Show values decrypts an entry for you; the values disappear after a minute or when you switch tabs, and every reveal is logged. Copied values are cleared from the clipboard after 30 seconds where the browser allows it. The generator creates random passwords or word passphrases; the strength meter rates every password. When you change a password, the last 20 stay under Previous passwords. Deleted entries go to the Trash; only Delete permanently removes the encrypted value.
Import reads exports from 1Password (CSV), Bitwarden (unencrypted JSON or CSV), Chrome, Edge, Firefox and Safari (CSV). Delete the export file afterwards. Export writes every entry into one file encrypted with your passphrase, readable without meinKontext too.
Agents can neither see nor fill vault entries. The vault is stored encrypted; the meinKontext server can decrypt values to show them. This is not end-to-end encryption.
API access for integrations
Entries of the kind API access (button "API-Zugang", view "API-Zugänge") sit in the same list. They keep API credentials encrypted that integrations use on the server, for example for agents; their value can never be shown or copied. Add values on the Secrets account page, never in an agent conversation. Labels are searchable metadata: use a descriptive name and keep the token in the password field.
The account page lets the custodian replace a credential, pause use, re-enable it or revoke it permanently. Replacing a disabled credential keeps it disabled. Revocation stops local use; revoke the provider's token separately when needed.
A credential is not automatically usable by an integration. Select and bind it on that connection's trusted setup page. Shared connection users receive only the approved capability, not the underlying secret value.
For manual setup, supported integrations accept a bearer access token or a JSON
token set with access_token, optional expires_at (Unix milliseconds) and
optional scope. Prefer the connection's browser authorization where available;
it manages refresh credentials too. Custom authentication headers are not supported.
For a portable backup, choose encrypted export and supply a new passphrase. Store that passphrase separately from the file. The server cannot recover a lost export passphrase. The ordinary metadata export contains no secret values.
The MCP tools return metadata and the setup-page path only. secrets_query
searches labels and status. secrets_collections lists accessible collections.
secrets_setup points to /account/secrets.
Credentials are encrypted at rest and decrypted by the executing server for authorized use. This is not end-to-end encryption against that server.
Workspaces in the browser
Use the page header to select one of your personal Workspaces. All content shows everything you may access, including content without a workspace assignment. An empty workspace stays empty. Manage assignments under Workspaces. The selection also applies when navigating, searching and exporting within the plugin. Save unfinished changes before switching workspaces; switching closes the previous editors.
A workspace says where content lives and where an agent works; a bucket says who else may use it. The workspace selection in the browser is not a grant: it widens neither access rights nor MCP credentials. More about workspaces.