jev-browser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_MODEL | No | Override the TypeSafe model. Ignored when the OpenRouter key is used. | |
| JEV_API_URL | No | Override the TypeSafe endpoint. Ignored when the OpenRouter key is used. | |
| JEV_BROWSER | No | Run your own browser instead of Playwright's Chromium (chrome, chrome-beta, msedge, or the path to any Chromium-based browser's executable). | |
| JEV_BROWSER_LOG | No | Set to 1 to print per-round decisions to stderr. | |
| TYPESAFE_API_KEY | No | Your TypeSafe System One API key. When both keys are set, TYPESAFE_API_KEY wins. | |
| JEV_BROWSER_HEADED | No | Set to 1 to show the browser window while it works. | |
| OPENROUTER_API_KEY | No | Your OpenRouter API key. Pass this instead of TYPESAFE_API_KEY to use Jev on OpenRouter; calls are billed to your OpenRouter account. When both keys are set, TYPESAFE_API_KEY wins. | |
| JEV_BROWSER_PROFILE | No | Directory for a persistent browser profile so logins survive restarts. Use a dedicated directory, since Chrome won't be automated with your everyday profile. | |
| JEV_BROWSER_NO_INSTALL | No | Set to 1 to turn off the Chromium download on first use. |
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
ActivityMaintained
ResponsivenessNo issues