Charlotte
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Disables the Chromium sandbox (enabled by default since v0.7.0). Set to 1 where the kernel sandbox is unavailable, e.g. containers or when running as root. Equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file. | |
| CHARLOTTE_OUTPUT_DIR | No | The directory where large tool results and artifacts (screenshots, output_file results) are written. Equivalent to "output": { "dir": ... } in the config file. Defaults to ./charlotte-output. | |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that runs on every new document before page JS. Equivalent to the repeatable --init-script <path> CLI flag or the browser.initScripts config key. | |
| CHARLOTTE_CDP_ENDPOINT | No | The Chrome DevTools Protocol endpoint URL to connect Charlotte to an existing browser instead of launching its own headless Chromium instance. |
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