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