A customer cannot get in
Sarah Chen, support engineer at Acme Ltd, asked why a customer could not sign in. Memtro found the user locked after failed attempts, with their last successful sign-in two days earlier, and listed their organisations.
When did this user last sign in, and which organisations are they in?
Clerk connects Memtro to user management for one instance. It reads users with name, primary email, whether banned or locked, and last sign-in and activity, and a user's sessions and organisation memberships. It reads organisations with member counts, an organisation's members and roles, and its invitations. When asked, and once an administrator has granted the action by name, it can ban or unban a user, lock their sign-in or lift the lock, revoke a session, delete a user, add, re-role or remove an organisation member, and invite somebody or revoke an invitation. Production and development each need their own connection.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Clerk tool, reads what it needs, and answers with the source cited.
These tools change something in Clerk. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Clerk, choosing the same kinds; the tab shows Clerk's own steps. Each event can start a job, with the event as its input. Clerk signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Clerk 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.
When did priya@acme.com last sign in?
Which users are banned or locked?
Who are the admins of the BigCo organisation?
Which organisation invitations are still pending?
Make Dan Fletcher an admin of the Northwind organisation
Sarah Chen, support engineer at Acme Ltd, asked why a customer could not sign in. Memtro found the user locked after failed attempts, with their last successful sign-in two days earlier, and listed their organisations.
Maya Okafor, customer success manager at Northwind, asked Memtro to make the new office manager at BigCo an admin of their organisation. Memtro changed the member's role in Clerk, which took effect from their next request. Nobody was emailed.
The teams that lean on Clerk most, a question each of them asks, and what they connect beside it.
A record in Clerk 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 Clerk Dashboard, choose the instance, production or development, and open Configure → API keys → Secret keys.
Copy a secret key, which starts sk_live_ or sk_test_. It has full access to its instance and Clerk offers no narrower key, so connect it only where an administrator has agreed.
In Memtro, open Connections → Clerk and paste it into Secret key.
Ask your first question: when did priya@acme.com last sign in?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Clerk tools are the same everywhere.
Only when you ask, and only what it has been granted: ban a user (signs them out everywhere, revokes their OAuth grants and stops them signing in); unban a user; lock a user's sign-in until the lock expires; unlock a user; revoke one of a user's sessions; delete a user (permanent); add an existing user to an organisation with a role; change an organisation member's role; remove a member from an organisation; invite somebody to an organisation (Clerk emails them a join link); revoke a pending organisation invitation. 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.
Secret key. In the Clerk Dashboard, choose the instance, production or development, and open Configure → API keys → Secret keys.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Clerk, choosing the same kinds; the tab shows Clerk's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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