Re:Vault MCP · your dashboard
Open your dashboard in the browser
Your key opens two doors into the same workspace. One is the set of tools inside Claude. The other is a dashboard you read in a browser: who you are writing to, which campaigns are running, what your profile sent today, who answered. Same numbers, same people, one place to look.
Address: re-vault.io/app. The key is the one from your connection email, it starts with rv_. Signing in takes about fifteen seconds. The address bar then shows the server your workspace runs on, and the card you land on is the one described below.
1. Sign in with the key you already have
Open re-vault.io/app
One card, two fields. Access method: pick MCP key. It runs in any browser and takes the key you already carry.
Paste the key
The same
rv_key that connects Claude, copied from your email. Press Open workspace and your workspace opens.Come back any time
The session lasts twelve hours, then the card asks for the key again. Keep the key out of shared screens and repositories.
2. What each screen shows
| Screen | What you read there |
|---|---|
| Overview | People opened, invitations sent, invitations accepted, conversations started, and the last thirty days day by day. |
| Targeting | Every person in your workspace with title, company and profile, and the campaign each one came from. |
| Senders | Your LinkedIn profile, its daily ceiling, how much is queued and how much has already gone out. |
| Conversations | Full threads with the people who answered, ordered by who wrote last. |
| Replies | What came back and what is waiting for your word. |
| Suppression | The companies and people your campaigns leave alone. |
The screens read the same tables the tools read, so a number here and a number in Claude come from one place. In a workspace where sending has not started yet, the screens open with zeroes and fill as the first batch goes out.
3. Reading and changing
The key opens the workspace for reading: numbers, people, campaigns, threads. Changing texts, approving a list before it goes out and handling the card belong to a member of the workspace, and membership comes as a one time invitation to your email.
Ask Dmitry for the invitation and name the address it should go to. The code lives thirty minutes, opens the same workspace and remembers you afterwards.
If it does not open
The card asks for an active key
The key has been replaced or its window has closed. Write to Dmitry and a fresh one comes back the same day.
It asks for the key again
Twelve hours have passed since you signed in. Paste the same key and carry on.
The screens are empty
Nothing has been queued in this workspace yet. Ask Claude in your chat to build the first batch, and these screens fill as it works.