Charlotte
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Set to 1 to disable the Chromium sandbox (equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file). Required where the kernel sandbox is unavailable, e.g. containers or bare-metal root. | |
| CHARLOTTE_OUTPUT_DIR | No | Directory where tool output artifacts (e.g. screenshots and large result sets written via output_file) are stored. Equivalent to the "output": { "dir": ... } config setting. | |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that runs on every new document before page JS. Equivalent to the browser.initScripts config setting or the repeatable --init-script <path> CLI flag. | |
| CHARLOTTE_CDP_ENDPOINT | No | Chrome DevTools Protocol endpoint to connect to instead of launching a bundled headless Chromium. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues