Claude Connector
Using Killswitch with Claude
Killswitch connects to Claude Desktop and claude.ai over MCP, so Claude can help draft notes, organize your Library, and propose a deadman switch — scoped to a session you start and can end at any time.
What the connector is
The Killswitch connector is an MCP (Model Context Protocol) integration that lets Claude read and write your Killswitch content on your behalf — through the same account and permission model as the web app, not a separate copy of your data. It's opt-in: nothing about the connector changes how Killswitch works if you never connect it.
Content Claude can reach is stored the same way as everything else in Killswitch — encrypted at rest and in transit.
Connecting Claude to Killswitch
- Create your Killswitch account. You'll need an account before Claude can connect to anything.
- Add the connector. In Claude Desktop or claude.ai, go to Settings → Connectors → Add custom connector and paste your Killswitch connector URL, which you'll find in Killswitch under Settings → Connector Sessions .
- Approve the connection and its scopes. Claude opens your browser to sign in to Killswitch and shows you the specific scopes it's requesting — notes, documents, switches, and/or beneficiaries. Approve only what you're comfortable granting.
- Unlock for Claude when you want AI help. Back in Killswitch's Connector Sessions tab, choose a session length (1 or 4 hours) and click "Unlock for Claude." Claude can only read or write your content while that session is active.
Approving scopes
When you approve the connection, Claude requests access in four independent scopes. Grant only the ones you want Claude working with — each is checked separately on every write:
Notes
Create and edit notes and journal entries, and create notebooks and folders in your Library.
Documents
Organize uploaded files in your Library — move or reorder them into folders and notebooks.
Switches
List your deadman switches and their check-in status, and propose a new switch or a change to an existing one.
Beneficiaries
List your beneficiaries and add a new one.
Session-scoped access, not a per-file setting. Every scope you approve is still gated by your connector session: while a session is unlocked, Claude can use the scopes you granted; once it ends, none of them work. There's no separate "hide this file from AI" toggle — access follows the session, not individual items.
See how Killswitch encrypts your data →What Claude can do
- List your deadman switches and their current check-in status, schedule type, and grace period.
- Draft and propose a new deadman switch, or propose changes to an existing one — you always review and confirm the final setup in the Killswitch app before it counts.
- Create and edit notes and journal entries, in Markdown or plain text.
- Create notebooks and folders, and organize items — move a document, note, or entry into a folder or notebook, or reorder it.
- List and read your notes, journal entries, and document metadata.
- List your beneficiaries, and add a new one.
A few additional tools are admin-only — if your account isn't an admin, they simply won't appear in Claude's tool list.
What Claude cannot do
- Check you in, fire, pause, or disarm a deadman switch. This is a hard rule in Killswitch's code, not just a missing feature — those actions always require you, in the Killswitch app or via a signed check-in link, never Claude.
- Delete a switch, a beneficiary, or anything in your Library.
- Read the actual contents of an uploaded file (a PDF, a recording) — Claude can see a document's name and where it's organized, but not its binary content.
- Access anything at all without an active, unlocked connector session — every request Claude makes is refused the moment your session ends.
Session mechanics
Clicking "Unlock for Claude" starts a time-boxed session — 1 hour or 4 hours, whichever you pick. While it's open, Claude can use whatever scopes you approved. When it expires, or you end it early, Claude loses access immediately: every tool call it makes is refused until you unlock again.
You can have more than one active session (for example, Claude Desktop and claude.ai at once), and each one is listed separately in Killswitch under Settings → Connector Sessions with its own expiration time.
Revoking access
Go to Settings → Connector Sessions in Killswitch, find the session you want to end, and click Revoke . Access is cut off immediately — Claude can't read or write anything on that session again, even if time was left on its clock. You can also just let a session run out; it stops working on its own once it expires.
Only you (or the schedule) can fire a switch. See the Deadman Switches guide for the full reminder ladder and firing mechanics, and the Claude connector overview for the marketing pitch and example prompts.
Ready to connect Claude?
Start a free trial, then connect Claude from Settings.
Start Free 30-Day Trial30 days free · No charge until day 31 · Cancel anytime