cloak-auth-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOAK_AUTH_REQUIRE_TOKEN | No | Set to '1' to require a pairing token for WebSocket connections. Default is '0'. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_list_sitesA | List registered Chrome authentication sources, whether the extension bridge is connected, and each site's allowed Cloak targets. |
| auth_sync_to_cloakB | Capture an allowlisted login state from the connected Chrome extension and import it into an allowlisted Cloak profile. Raw authentication secrets are never returned. |
| auth_verify_cloakB | Verify whether an allowlisted Cloak profile is logged in to a registered site. |
| auth_clear_cloakA | Clear one registered site's authentication state from a Cloak profile. Requires confirm=true. |
| cloak_debug_openA | Open one headed CloakBrowser debug session for an allowlisted profile. Uses a single Free-plan browser session; open more sites with cloak_debug_tab. |
| cloak_debug_tabA | Open another HTTPS tab in the active Cloak debug session via local CDP attach. Does not start a second browser process. |
| cloak_debug_listA | List page tabs in the active Cloak debug session. |
| cloak_debug_statusA | Show whether a Cloak debug session is active. |
| cloak_debug_closeA | Close the active Cloak debug session and release the Free-plan browser seat. |
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 9 tools
Tools cleanly separate into auth management (list_sites, sync, verify, clear) and debug session management (open, tab, list, status, close). Each tool has a distinct resource and action with no meaningful overlap or ambiguity.
Consistent use of prefixes (auth_, cloak_debug_) helps grouping, but the verb/noun pattern is mixed: most use verb_noun (cloak_debug_open, auth_verify_cloak), while a few use bare nouns (cloak_debug_status, cloak_debug_tab). The inconsistency is noticeable but not chaotic.
Nine tools is well-scoped for an auth bridge with debug capabilities. Each tool addresses a specific workflow step, and there are no redundant or filler tools.
Covers the core lifecycle for auth sync (list, sync, verify, clear) and debug session management (open, tab, list, status, close). Minor gaps remain, such as no explicit site removal or screenshot capability, but agents can achieve main workflows without dead ends.