Best for
- Users who want to manage MCP servers from a desktop application
- Users connecting ChatGPT, Claude, Qwen, or self-hosted LLM backends
- Developers exploring MCP integrations and testing applications
T
53FMRS · D
Based on the README, TUUI is an open-source desktop MCP client maintained by AI-QL, not an MCP server. The repository does not provide a server manifest or tool identifiers for TUUI itself.
TUUI is a desktop MCP client and local LLM chat application for integrating AI tools through the Model Context Protocol and dynamically orchestrating cross-vendor LLM APIs. It supports MCP tools, prompts, resources, sampling, elicitation, registry discovery, and MCP Bundles (.mcpb).
Tools
The tool list has not been reviewed yet.
Setup
Download and run the application for Windows, Linux, or macOS from GitHub Releases. Developers can build the project using the English or Chinese installation guide in the repository. Before using MCP features, configure an LLM backend that supports tool calling; depending on the MCP server type, Node.js, Python with UV, or Docker may also be required.
Fit and risk
Not for
- Users seeking an MCP server callable by another MCP client
- Users who do not want to configure an LLM backend or run local MCP server processes
- Users seeking a server directory with a predefined tool list
Required permissions
- Access to configured LLM APIs or self-hosted backends
- Permission to launch configured local commands and runtimes for MCP servers
- Network access to configured remote MCP servers and related services
- Access to read and save application configuration and local storage
Risks and side effects
- Configured MCP servers are launched and executed according to their settings, so behavior depends on those servers and commands
- Configured LLM APIs may process chat content, tool-call content, and API keys
- Remote MCP connections and OAuth configuration may be affected by network, browser-cache, or callback issues
- Initial installation or updates of npx, uv, or uvx runtimes may cause connection timeouts
Troubleshooting
- Verify that commands such as uv, uvx, and npx run correctly on the current system
- For ENOENT errors, run the MCP server locally and configure its absolute path
- On macOS with NVM, check MCP command paths and permissions
- For initialization timeouts beyond 90 seconds, manually install the relevant pip or npm dependencies first
- For remote authentication failures, check OAuth auto-redirect behavior and clear the authentication-page cache
Use cases
Connecting to and using MCP server tools
Configuring and orchestrating multiple LLM APIs
Tracing MCP tool calls
Exploring MCP primitives, elicitation, and MCP Bundles
Supported clients
Supported clients have not been confirmed yet.