Jev Decision MCP

A local stdio MCP server exposing one tool, jev_decide, for typed decisions through any SDK-compatible decision API endpoint. Point it at an endpoint with BASE_URL and MODEL; there is no provider preset, host allowlist, or model allowlist. Written in TypeScript with the official MCP SDK and the @typesafe-ai/sdk typed-decision SDK.

Independent community project; not affiliated with the SDK vendor. Licensed under MIT.

Batch independent questions over the same context in one call. Answers retain their question IDs. The MCP returns judgments and token usage; the caller owns thresholds, escalation, and action execution.

Requirements

• Node.js 22 or newer, with npm available on your PATH.
• An MCP client that supports local stdio servers.
• An API key for the decision endpoint you configure (API_KEY). It is required for decision calls only — the tool can be discovered without one.

What “SDK-compatible” means here. Compatibility is the typed-decision contract of the @typesafe-ai/sdk: the endpoint must implement the SystemOne request (POST {BASE_URL}/v1/systemone) that returns typed choice/score/noul answers with probability distributions and usage counts.

Install from npm

The npm package includes the built server. npx downloads it on first use and runs it without cloning or building:

npx -y [email protected]

Add the following to your MCP client’s configuration, replacing the placeholders with your endpoint’s values. For clients that use mcpServers JSON:

{
  "mcpServers": {
    "jev": {
      "command": "npx",
      "args": ["-y", "[email protected]"],
      "env": {
        "API_KEY": "YOUR_API_KEY",
        "BASE_URL": "https://api.example.com/decisions",
        "MODEL": "your-model-name"
      }
    }
  }
}

Alternatively, set API_KEY, BASE_URL, and MODEL in the environment that launches your client and omit env if the client forwards those variables. Restart or reload your client’s MCP servers after saving the configuration; the tool appears as jev_decide.

If the host cannot resolve npx, use its platform-specific launcher or absolute path as documented by that host. GUI applications may have a different PATH from your terminal.

The server communicates over stdio; starting it in a terminal waits for an MCP