Jev Decision Gate
by f-tiger
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --allow-jev | No | Enable outbound Jev model calls in the MCP server. Jev is disabled by default; add `--allow-jev` at startup only when outbound model calls are authorized and the process can read your key. | false |
| --data-root | Yes | Absolute path to the authorized Issue JSON directory that the MCP server is allowed to read. Passed to jev-gate-mcp at startup, e.g. `jev-gate-mcp --data-root /absolute/path/to/authorized-json`. | |
| --max-calls | No | Maximum number of Jev calls allowed at MCP server startup, used together with `--allow-jev` (e.g. `--allow-jev --max-calls 20`). | 20 |
| TYPESAFE_API_KEY | No | TypeSafe API key for Jev. Set through your local environment or secret manager; required only when Jev is enabled via `--allow-jev`. Do not paste a key into an issue, model chat, repository or MCP configuration committed to Git. |
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
ActivityNo data
ResponsivenessNo issues