An access review
Sarah Chen, IT manager at BigCo, asked who could reach the finance collection before the quarterly audit. Memtro read the collection's groups and their access levels, then listed each group's members by name and email.
Who has access to our finance collection in Bitwarden, and who was revoked this month?
Bitwarden shows you your organization's members with their role and status, and the groups they belong to. Memtro also reads which collections each group reaches and at what level, the organization's event log and its policies. When asked and granted, it can invite, re-invite, revoke, restore or remove a member, or change a member's role or groups. It can create, rename or delete a group, set its members, set which groups reach a collection, or delete a collection. It never reads vault items or passwords, and only an organization owner can view the API key.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Bitwarden tool, reads what it needs, and answers with the source cited.
These tools change something in Bitwarden. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Bitwarden is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who can reach the finance collection, and at what level?
Which members are still invited but not confirmed?
Who was revoked or removed this month?
Is two-step login required by policy?
Revoke Tom Reilly's access to the organization.
Sarah Chen, IT manager at BigCo, asked who could reach the finance collection before the quarterly audit. Memtro read the collection's groups and their access levels, then listed each group's members by name and email.
Dan Fletcher, operations lead at Acme Ltd, asked Memtro to revoke a departing contractor's access. With the action granted, Memtro revoked the member. They lost access to the collections at once, but stayed listed so they could be restored.
The teams that lean on Bitwarden most, a question each of them asks, and what they connect beside it.
A record in Bitwarden is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Bitwarden web vault, open Admin Console → Settings → Organization info → API key → View API key. Only an organization owner can view it, and a personal key does not work.
Open Connections → Bitwarden in Memtro and paste the client_id and client_secret. Set Server to us, eu or your self-hosted host name.
An administrator grants actions such as revoke a member or delete a group by name, only to the teams that run access.
Ask who can reach the finance collection.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Bitwarden tools are the same everywhere.
Only when you ask, and only what it has been granted: invite a person to the organization by email; re-send a member's invitation; revoke a member's access (reversible); restore a revoked member; remove a member from the organization; change a member's role; set which groups a member belongs to; create a group; rename a group or change its collection access; delete a group; set a group's members; set which groups can reach a collection; delete a collection and its items. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
client_id, client_secret and server. In the Bitwarden web vault, open Admin Console → Settings → Organization info → API key → View API key. Only an organization owner can view it, and a personal key does not work.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time