Charlotte
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Disables the Chromium sandbox. The sandbox is enabled by default as of v0.7.0; set CHARLOTTE_NO_SANDBOX=1 (equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file) in environments where the kernel sandbox is unavailable, such as containers or when running bare-metal as root. | |
| CHARLOTTE_OUTPUT_DIR | No | Directory where tool output is written (equivalent to the output.dir config file setting, e.g. "./charlotte-output"). | |
| 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 used to connect to an existing browser instead of launching a new 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