chrome-session-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PROFILE | No | Pin the Chrome profile. | |
| CHROME_USER_DATA | No | Pin the Chrome user-data directory. | |
| CHROME_SESSION_MCP_CACHE | No | Cache directory (default `~/.cache/chrome-session-mcp`). | |
| CHROME_SESSION_MCP_CONFIG | No | Config file path. | |
| CHROME_SAFE_STORAGE_PASSWORD | No | Linux: the keyring password, if `secret-tool` cannot find it. | |
| CHROME_SESSION_MCP_LOGIN_WAIT | No | Seconds to wait for a login. | |
| CHROME_SESSION_MCP_NO_BROWSER | No | Set to `1` to never open Chrome. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools over web apps the user is logged in to in Google Chrome. Each tool authenticates with the
user's own Chrome cookies; no API tokens. Call list_connectors to see the configured connectors
and pass a connector name as instance when several of one type exist.
If a session has expired, the tool opens Chrome on the login page and waits (a few minutes) for the user to log in, then retries. If it still fails, ask the user to finish logging in and retry. Tools are read-only unless the connector has allow_write; write tools ask before each call. To show the user a page, use open_in_browser: it opens in their Chrome, already logged in. Large results are written to a file under ~/.cache/chrome-session-mcp/ and the path is returned.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectorsA | List the connectors in the config file (name, type, base URL, whether writes are enabled), plus any config errors. Call this first to learn which instance names to pass to other tools. |
| auth_statusA | Check which connectors currently have a working Chrome session, without opening a browser. |
| loginA | Open Chrome on a connector's login page and wait until its session works. Other tools already do this by themselves when they hit an expired session; use this to log in ahead of time. |
| open_in_browserA | Open a URL in the user's own Google Chrome so they can look at it themselves (a dashboard, a failing build, a page you just edited). It opens in the Chrome profile that holds that site's cookies, so the page is already logged in. Only http/https URLs. |
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 4 tools
Each tool targets a distinct concern: config inspection (list_connectors), passive session checking (auth_status), active login (login), and opening a URL for the user (open_in_browser). The only mild overlap is auth_status vs login, but descriptions clearly separate passive checking from performing a login.
Names use three different patterns: verb_noun (list_connectors, open_in_browser), noun_phrase (auth_status), and a bare verb (login). Still readable and each name hints at its purpose, but the convention is mixed.
Four tools are tightly scoped to the server's apparent purpose of managing authenticated Chrome sessions. Each tool has a clear, non-redundant role with no filler.
The session lifecycle (discover connectors, check status, log in, use the session to open pages) is covered. Minor gaps exist, such as no logout/clear-session or a tool to programmatically read page content from a connector, but agents can work around these.