Charlotte
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARLOTTE_NO_SANDBOX | No | Disables the Chromium sandbox (equivalent to the --no-sandbox CLI flag or "browser": { "noSandbox": true } in the config file). The Chromium sandbox is enabled by default; set CHARLOTTE_NO_SANDBOX=1 where the kernel sandbox is unavailable, e.g. in containers or when running Charlotte as root. | false |
| CHARLOTTE_OUTPUT_DIR | No | Directory where Charlotte writes output artifacts (equivalent to the "output": { "dir": ... } config key). | ./charlotte-output |
| CHARLOTTE_INIT_SCRIPT | No | Path to a script that should run on every new document before page JavaScript (equivalent to "browser.initScripts" or the repeatable --init-script <path> CLI flag). | |
| CHARLOTTE_CDP_ENDPOINT | No | CDP endpoint used to connect Charlotte to an existing Chromium instance instead of launching its own. |
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