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. |
| 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 10 tools
Each tool has a clearly distinct target and action: local sessions (hide_session, list_sessions), browser chats (hide_browser_chat, list_browser_chats), and vault contents (list_hidden, read_hidden, restore_hidden). The list/unlock/lock/status tools are also unambiguous, so an agent can easily select the right operation.
Names are consistently snake_case and mostly follow a verb_noun pattern (hide_session, list_browser_chats, unlock_vault). The only deviation is applock_status, which is noun_status rather than verb_noun, but it remains readable and predictable.
The 10 tools sit comfortably in the ideal 3–15 range for a focused privacy/locking utility. Each tool corresponds to a distinct operation, and there is no obvious redundancy or missing essential operation.
The set covers the full hide/list/read/restore/unlock/lock lifecycle for local sessions and browser chats, plus status reporting. Minor gaps exist: no permanent delete from vault, no search/filter for hidden items, and read_hidden appears limited to local sessions, but core workflows are covered.