Public Browser
by Silbercue
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | Path to Chrome binary (overrides auto-detection) | |
| SILBERCUE_CHROME_PORT | No | CDP debugging port | 9222 |
| PUBLIC_BROWSER_PROFILE | No | Chrome profile name or path to use | |
| PUBLIC_BROWSER_TELEMETRY | No | Opt-in: upload anonymised Cortex patterns to the community endpoint | |
| SILBERCUE_CHROME_PROFILE | No | Chrome user profile directory (auto-launch only) | |
| SILBERCUE_CHROME_HEADLESS | No | Opt-in headless mode for CI/server environments | false |
| SILBERCUE_CHROME_AUTO_LAUNCH | No | Auto-launch Chrome if no running instance found | true |
| PUBLIC_BROWSER_TELEMETRY_ENDPOINT | No | Override the telemetry collection endpoint (must be HTTPS) | https://cortex.public-browser.dev/v1/patterns |
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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Silbercue/public-browser'
If you have feedback or need assistance with the MCP directory API, please join our Discord server