jevpilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_API_KEY | Yes | Your API key for the selected Jev provider (TypeSafe API or OpenRouter). | |
| JEV_PROVIDER | Yes | The Jev model provider, e.g. openrouter or typesafe. Use JEV_PROVIDER=typesafe for a TypeSafe key. | |
| JEVPILOT_DISPLAY | No | Set to headed to use a headed browser (off-screen on Windows, Xvfb or an existing display on Linux). Default is headless. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_runA | Open a new browser session and work toward a goal. Jev acts fast on its own and hands back early with a question when unsure; continue with browser_act / browser_resume from the returned snapshot. Returns a session ID and a status; handoff statuses include a concrete question for the agent or user. Reuse the session with browser_resume, browser_observe, browser_act, and browser_close. |
| browser_resumeA | Continue an existing session after a handoff. Supply missing values, refine the goal, or approve one pending irreversible action; approval is scoped to that action. |
| browser_observeA | Read the current page in an existing session without taking action. Use full detail when the compact snapshot omits needed content. A screenshot path may be returned for handoffs when safe. |
| browser_actB | Perform manual browser operations against current element refs in an existing session. Returns a fresh snapshot, so a separate browser_observe is not needed after it. The orchestrator rechecks targets and applies the same domain and irreversible-action gates. |
| browser_navigateB | Navigate the selected session tab within its domain allowlist. |
| browser_tabsC | List, select, or close tabs owned by a browser session. |
| browser_closeA | Close a browser session and its tab, and delete its temporary handoff files. The shared browser remains available for other sessions. |
| jev_decideC | Pass a state and typed questions directly to the configured decision port. This does not create or change a browser session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools are mostly distinct: browser_run creates sessions, browser_observe reads, browser_act performs manual ops, browser_navigate handles within-session navigation, and browser_tabs manages tabs. The main overlap is between browser_resume (handoff continuation/approval) and browser_act (manual element operations), which both act on existing sessions and could occasionally be confused despite clarifying descriptions.
Seven of eight tools follow a clear browser_verb snake_case pattern (browser_run, browser_observe, browser_act, etc.), which is predictable and readable. jev_decide breaks the browser_ prefix convention, but it represents a separate decision-port domain, making the deviation minor and understandable.
Eight tools is well-scoped for a browser automation server with handoff support. Each tool earns its place across the session lifecycle (create, resume, observe, act, navigate, tabs, close) plus one distinct decision tool, with no obvious redundancy or missing role.
The surface covers the full browser session lifecycle: creation (browser_run), continuation (browser_resume), reading (browser_observe), manual action (browser_act), navigation (browser_navigate), tab management (browser_tabs), and teardown (browser_close), plus decision support. Minor gaps exist around multi-session discovery or session listing, but core workflows are fully supported.