JevRelay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEVRELAY_API_KEY | No | API key for the JevRelay provider. Required when JEVRELAY_PROVIDER=jevrelay. | |
| JEVRELAY_API_URL | No | API URL for the JevRelay provider. Defaults to https://api.jevrelay.com/v1/decide. Required when JEVRELAY_PROVIDER=jevrelay. | |
| OPENROUTER_MODEL | No | OpenRouter model to use, e.g., openai/gpt-4o-mini. Required when JEVRELAY_PROVIDER=openrouter. | |
| TYPESAFE_API_KEY | No | API key for TypeSafe Jev inference. Required when JEVRELAY_PROVIDER=typesafe. | |
| JEVRELAY_PROVIDER | No | Inference provider to use. One of: typesafe, openrouter, jevrelay. | |
| OPENROUTER_API_KEY | No | API key for OpenRouter. Required when JEVRELAY_PROVIDER=openrouter. |
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 |
|---|---|
| jevrelay_validateA | Validate a declarative Jev Script without executing it. |
| jevrelay_runA | Validate and execute a Jev Script locally with Playwright. Inference is used only for explicit decide steps. |
| jevrelay_statusB | Return the current status and partial output of a JevRelay run. |
| jevrelay_stopB | Request cancellation of a running JevRelay automation. |
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 4 tools
Each tool has a clearly distinct role in the script lifecycle: validate checks syntax, run executes, status reports progress, and stop cancels. Although run also validates, its execution focus makes it distinct from validate-only.
All tools use the same jevrelay_ prefix and snake_case format with predictable verb/noun labels. The only minor variation is status being a noun, but it remains clear and consistent with the overall scheme.
Four tools is well-scoped for a script validation and execution service. Each tool covers a necessary lifecycle operation without redundancy.
The surface covers the core lifecycle: validate, run, check status, and stop. Minor gaps exist, such as listing past runs or retrieving full logs/artifacts, but agents can work around them.