other / agent

Jev Chat

A local web demo of a Jev-classifier command bar with MCP tools and code-built replies.

Repository owner w3cj

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: A local web demo of a Jev-classifier command bar with MCP tools and code-built replies.
Runs in: MCP server, Web service
Operating systems: Not stated
Needs: Runtime: Node.js 24+ and pnpm 11; Needs internet: Yes; Needs accounts or API keys beyond your agent: Yes
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type: Agent
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README, it needs Node 24 or later and pnpm 11 and runs as a local development setup, with the server on port 8787 and the web app on port 5173. The README says to open the app on the same machine. The README lists MCP servers for weather (Open-Meteo), units and maths, Wikipedia, recipes (TheMealDB), Brave Search, Todoist and Home Assistant. The README says the app works in English only.
External costs: The README says TYPESAFE_API_KEY is required and that Jev is a paid API. It gives no price. Brave Search needs BRAVE_API_KEY, Todoist needs TODOIST_API_KEY, and Home Assistant needs HASS_URL and HASS_TOKEN. The README says Brave Search and Todoist are used through their own MCP servers and your own accounts. It says the Open-Meteo free API is for non-commercial use and that the default TheMealDB test key is for development and educational use.
Permissions: The README's setup installs dependencies with pnpm and configures a TypeSafe API key. The README also describes credentials for Brave Search, Todoist and Home Assistant and a recipe-service key for uses beyond the default test key. The README describes requests to Jev and MCP servers for weather, units, Wikipedia, recipes, search, tasks and home-device actions. The README says adding or completing Todoist tasks and Home Assistant actions that could reach locks, covers or unknown devices require confirmation cards. The README warns that model routing can choose the wrong tool and that fetched content is untrusted. The README says the unauthenticated API binds to 127.0.0.1 and restricts accepted hosts to localhost addresses.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms. The README says Open-Meteo weather and GeoNames-based geocoding data use CC BY 4.0 and Open-Meteo's free API is for non-commercial use. The README says Wikipedia article text and the repository's Wikipedia fixtures use CC BY-SA 4.0. The README says TheMealDB's default test key is for development and educational use and other uses need your own key. The README says Brave Search and Todoist use their own MCP servers and your own accounts.
Interface: web

Code on GitHub

w3cj/jev-chat

MIT

TypeScript114 stars24 forksLast pushed 18 Sept 2026 UTC

A tool calling chat bot built with Jev and no LLM.

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

Skill folders in this repository (3)

Folders that contain a SKILL.md file, from GitHub's file list on 13 Oct 2026 UTC.

View on GitHub ↗

What it does

Jev Chat is a chat-shaped command bar connected to MCP tools. The README describes Jev, a TypeSafe classifier, choosing tools, arguments, confirmation requirements and reply types from supplied options. The README says application code calls the MCP servers and constructs replies from user text and tool results.

The README warns that routing can select the wrong tool, span or line and that tools can return incorrect data. The README describes an inspector showing requests, questions, probabilities and application decisions.

The README lists weather, units and maths, Wikipedia, recipes, Brave Search, Todoist and Home Assistant tools. The README says Jev requires a paid API key, while Brave Search, Todoist and Home Assistant need additional configuration. The README calls the repository a demo and proof of concept and describes extending it through adapters.

Who it is for

Developers who want to read, run or extend a demo of a tool-calling chat bot built on the Jev classifier and MCP servers.

Example tasks

Ask what the weather in Denver is tomorrow.
Ask for 350F in celsius or a 20% tip on $64.
Ask how tall Mount Rainier is.
Ask for something vegan for dinner, then ask how to make the first one.
Open the inspector to see the questions and probabilities behind a reply.

Getting started

The README says to run pnpm install, then cp .env.example .env and fill in the keys you have, then pnpm dev. The README says only TYPESAFE_API_KEY is required. The README says corepack enable picks up the pnpm version pinned in package.json. The README has the exact commands.

Limitations

The README requires Node 24 or later and pnpm 11. The README says pnpm install needs a C++ toolchain if no prebuilt better-sqlite3 binary matches your platform. The README says TYPESAFE_API_KEY is the only required key, Jev is paid, and without that key the app starts but every message gets an error reply. The README lists additional settings for Brave Search, Todoist and Home Assistant. The README says the API listens on 127.0.0.1 only and refuses requests addressed to, or sent from a page on, any host other than localhost, 127.0.0.1 or [::1]. The README calls this a dev setup and says nothing serves the built files. The README says the app works in English only, each message runs one tool, compound requests are not handled yet and there is no timer tool. The README calls the repository a demo and proof of concept and says the author will not accept pull requests for new features. The repository can change at any time; check its README before you install.

Data practices

The README says the app stores conversations and every trace in SQLite at apps/server/jev-chat.db, and that you delete the file to start over. It says the web app keeps UI preferences in localStorage. The README's main-request diagram shows the message, recent chat, shown results, pending action and options including home devices going to Jev. The README says Jev is a paid API requiring a TypeSafe key and that application code calls the connected MCP servers. The README does not describe telemetry.