amidabuddha/jev-decision-mcp

A local stdio MCP server exposing one tool, **jev_decide**, for typed decisions through the official TypeSafe API. Written in TypeScript with the official MCP and TypeSafe SDKs.
Independent community project; not affiliated with TypeSafe. Licensed under MIT.
| Question | Use it for | Result |
| --- | --- | --- |
| choice | Choose a label or candidate | Choice, probabilities, confidence |
| score | Rate a single dimension on 2–10 ordered levels | 0-based score, probabilities, legend, confidence |
| noul | Judge whether a condition holds | Probability of yes, from 0 to 1 |
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 from TypeSafe Console. Use an official TypeSafe key; OpenRouter and third-party gateway keys are not supported.
Install from npm
The npm package includes the built server. npx downloads it on first use and runs it without cloning or building:
Add the following to your MCP client's configuration, replacing YOUR_TYPESAFE_API_KEY with your key. For clients that use mcpServers JSON:
Alternatively, set TYPESAFE_API_KEY in the environment that launches your client and omit env if the client forwards that variable. 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
client rather than opening a web page. The npm installation does not read a
.env from the caller's working directory.
To install the executable globally instead:
Then use "command": "jev-decision-mcp" with no arguments in your MCP client, and supply the same API key.
Install via Glama
Open Jev Decision MCP on Glama to view its README, tool schema, and source. For local installation, use the npm configuration above, or follow the listing's **GitHub Repository** link to download or clone the source and build it below. Glama lists this as a local stdio server; the listing URL is not an MCP connection endpoint.
Connect to Codex
For the npm package, merge this into your Codex config.toml:
Set TYPESAFE_API_KEY in the environment that launches Codex; env_vars forwards
its existing value to the server. Keep the host tool timeout above
JEV_TIMEOUT_MS / 1000. See official Codex MCP configuration.
Build from source
Clone the repository, install its dependencies, and compile the server:
You can also download the repository with **Code → Download ZIP** on GitHub, extract it, and run npm ci and npm run build in the extracted directory.
Copy .env.example to .env in that directory and set TYPESAFE_API_KEY, or supply the key through your MCP client's environment. The source build reads this .env regardless of its working directory; existing environment variables take precedence. Restart the server after changing it. .env is excluded from Git.
Configure your MCP client to run the built entry point: