Its value is as a bench: point it at a few servers and a few backends and watch what a tool call actually does, with a codebase small enough to modify. The author has since started a restructured successor, TUUI, so treat this one as the compact original rather than the actively growing app.
An MCP client, not a server. An Electron desktop app built to keep the code small enough to read, so the mechanics of MCP - connecting clients, listing tools, running a tool call - stay visible rather than buried.
- One app on Linux, macOS and Windows, buildable into your own packaged desktop application
- Model configuration by JSON file, against any endpoint that speaks the OpenAI SDK shape and supports function calls
- Several clients configured at once, each connected to a different MCP server
- A UI layer that can be lifted out for web use, so desktop and browser behave the same
- Apache-2.0, so you can fork it into your own product
Node.js. Clone the repository, edit config.json in src/main so the command and args point at servers that exist on your machine, then npm install and npm start. Building a packaged app is npm run build-app. Model access needs an API key in the interface configuration file you supply.
