AppLock
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| applock_statusA | Shows whether AppLock is set up, locked or unlocked, how many chats are hidden, and whether the browser extension is connected. |
| list_sessionsA | Lists local Claude Code and Antigravity chat sessions that are currently visible (not hidden), newest first, so you can find the one to hide. |
| hide_sessionA | Encrypts a Claude Code or Antigravity session into the vault and removes it from the app's history. Works while locked. Use id "current" for the Claude Code session you are running in; it is hidden as soon as that session ends. |
| list_browser_chatsB | Lists ChatGPT, Claude.ai and Gemini chats visible in the sidebar of the user's browser, as reported by the AppLock extension. Also says which chat is open right now. |
| hide_browser_chatA | Tells the AppLock browser extension to lock a web chat: it disappears from the sidebar and shows a lock screen if opened, until unlocked with Touch ID or the password. Use chat_id "current" for the chat open in the browser. |
| hide_on_phoneA | Turns AppLock's 'Hide on your phone too' on or off. When on, locked ChatGPT chats are also archived in the user's ChatGPT account, so they disappear from the chat list in the ChatGPT iPhone/Android/desktop apps (still listed under ChatGPT's Archived chats). Removing a lock in the browser unarchives it. Claude and Gemini have no archive. Needs the AppLock browser extension. |
| copy_to_vaultA | Saves the full transcript of ChatGPT or Claude chats into the encrypted AppLock vault, WITHOUT deleting them anywhere, so they can be read in the AppLock Vault phone app or with read_hidden. Use chat_id "locked" for every locked ChatGPT/Claude chat. Needs the browser extension with that site signed in. |
| unlock_vaultA | Unlocks hidden chats for a few minutes. Shows the Touch ID prompt on the user's Mac, or opens a local passphrase page in their browser. The user authenticates on their own device; never ask for the passphrase in chat. Waits up to 2 minutes. |
| lock_vaultA | Forgets the vault key immediately and re-locks web chats in the browser extension. |
| list_hiddenA | Lists everything in the vault (titles, sources, dates). Requires the vault to be unlocked. |
| read_hiddenA | Returns the transcript of a hidden local session without restoring it. Requires unlock. Note: the text becomes part of the current, visible conversation. |
| restore_hiddenA | Decrypts a hidden session back to its original place so it shows up in the app again (or unlocks a web chat in the extension). Requires unlock. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The 'hide' family (hide_session, hide_browser_chat, hide_on_phone, copy_to_vault) and the 'list' family (list_hidden, list_sessions, list_browser_chats) could initially look overlapping, but descriptions clearly scope each to a distinct target (local session vs browser chat vs vault vs phone archive). read_hidden vs list_hidden vs restore_hidden are also well differentiated by their stated effects.
Names follow a consistent snake_case verb_noun pattern (list_hidden, hide_session, restore_hidden, lock_vault, unlock_vault), which makes the set predictable. The lone deviation is applock_status, a noun-first status tool, but it's a recognizable convention for a query tool.
12 tools sit comfortably in the well-scoped 3-15 range. Each tool maps to a concrete operation (hide, list, read, restore, lock/unlock, copy, status) with no filler.
The set covers the full lifecycle: hide, list, read, restore, copy, lock, unlock, and status, with per-surface variants for local sessions and browser chats. Minor gaps exist (e.g. no way to permanently delete/clear a vault entry or search within hidden items), but core workflows are covered.