jev-in-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_API_KEY | No | The Jev API key (OpenRouter or TypeSafe). If not set, it is read from credentials.json in the config directory. | |
| JEV_IN_MCP_HOME | No | Overrides the configuration directory (default is ~/.config/jev-in-mcp). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_statusA | Which servers are connected, whether a Jev key is configured, and which tools each use_jev may use. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The single tool has a clear, distinct purpose.
The tool name 'jev_status' is clear and descriptive, and with only one tool there are no conflicting naming conventions to cause inconsistency.
The server exposes a single tool, which feels thin for a typical MCP server. However, it is appropriate for a status-only tool, so the count is borderline.
The status tool covers the key aspects of its domain: connection state, key configuration, and tool permissions. No obvious gaps for a status endpoint.