Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEBUGNoSet to * to enable verbose logs. Useful for submitting bug reports.
channelNoSpecify a different Chrome channel that should be used. The default is the stable channel version. Choices: stable, canary, beta, dev
logFileNoPath to a file to write debug logs to. Set the env variable DEBUG to * to enable verbose logs. Useful for submitting bug reports.
headlessNoWhether to run in headless (no UI) mode.false
isolatedNoIf specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed.false
viewportNoInitial viewport size for the Chrome instances started by the server. For example, 1280x720. In headless mode, max size is 3840x2160px.
chromeArgNoAdditional arguments for Chrome. Only applies when Chrome is launched by chrome-devtools-mcp.
browserUrlNoConnect to a running Chrome instance using port forwarding. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server.
proxyServerNoProxy server configuration for Chrome passed as --proxy-server when launching the browser. See https://www.chromium.org/developers/design-documents/network-settings/ for details.
executablePathNoPath to custom Chrome executable.
acceptInsecureCertsNoIf enabled, ignores errors relative to self-signed and expired certificates. Use with caution.

Schema

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

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/SHAY5555-gif/chrome-devtools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server