chrome-cookies-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | chrome.exe path (launcher only) | |
| CHROME_PROFILE | No | profile name (launcher only) | Default |
| CHROME_CDP_HOST | No | CDP host | 127.0.0.1 |
| CHROME_CDP_PORT | No | CDP remote-debugging port | 9222 |
| CHROME_USER_DATA_DIR | No | profile dir (launcher only) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cookiesA | Get cookies for a given domain from the running Chrome (via DevTools Protocol). Returns cookies whose domain equals or is a sub/parent-domain of the query, in the requested format. Chrome must be launched with --remote-debugging-port. |
| list_domainsA | List all distinct cookie domains currently present in the running Chrome, with cookie counts. Useful to discover which domains have cookies before calling get_cookies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-l-lambda/chrome-cookies-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server