TypeSafe MCP — devbux

Run it with npx -y @devbux/typesafe-mcp or bunx @devbux/typesafe-mcp, or install globally with npm install -g @devbux/typesafe-mcp and start the typesafe-mcp binary. It speaks MCP over stdio, so normally your MCP client launches it rather than you running it by hand.

Yes for tool calls. Create a key in the TypeSafe console and expose it as the TYPESAFE_API_KEY environment variable. The server still starts when the variable is unset so clients can list its tools, but each tool call then returns a clear error naming the missing variable instead of crashing.

Most clients accept a generic mcpServers JSON block with command npx and args -y @devbux/typesafe-mcp. Claude Code can add it with claude mcp add typesafe, and Cursor and VS Code use the same per-server fields, with VS Code reading a top-level servers key in .vscode/mcp.json.

jev_decide takes a state and a map of typed questions and returns all answers in one call. jev_choice, jev_score, jev_noul and jev_box each return a single answer under the name answer, and jev_list_models returns available model names, descriptions and release dates.

Errors such as a missing API key, HTTP 401, 403, 429 or 5xx responses, network failures and timeouts are returned as MCP tool errors with isError set and a message that includes the HTTP status. The message never includes your API key.

Yes. TYPESAFE_JEV_MODEL defaults to jev-latest and can be overridden by the optional model argument on the tools. jev_box defaults to jev-1.14.0, and jev_list_models shows which model ids are available.

Choice questions take 2-255 labelled options, score questions take an ordered scale of at least 2 levels, noul questions return a calibrated probability from 0 to 1, and box questions return bounding-box edges plus confidence. States, instructions and criteria accept structured JSON, and images can be passed in an assets map.