tuui and mcp-cli
These are complementary tools serving different interaction paradigms—a graphical desktop client versus a command-line interface—both enabling MCP server connections through different user workflows.
About tuui
AI-QL/tuui
A desktop MCP client designed as a tool unitary utility integration, accelerating AI adoption through the Model Context Protocol (MCP) and enabling cross-vendor LLM API orchestration.
Supports full MCP specification including tools, prompts, resources, sampling, and discovery via the MCP registry, with bundled .mcpb extension support for modular server composition. Built on Vue 3 with Electron for cross-platform desktop deployment, featuring dynamic LLM endpoint configuration that accepts multiple vendor APIs (OpenAI, Claude, Qwen, DeepInfra) through JSON-based server manifests and optional remote MCP server proxying via Cloudflare's mcp-remote protocol.
About mcp-cli
apify/mcp-cli
mcpc is a CLI client for MCP. It supports persistent sessions, stdio/HTTP, OAuth 2.1, JSON output for code mode, proxy for AI sandboxes, and much more.
Exposes full MCP protocol capabilities—instructions, resources, prompts, async tasks, and dynamic server discovery—through intuitive shell commands and JSON output for scripting. Built as a lightweight stdio/HTTP client with persistent session management and an embedded proxy server for secure AI sandboxing. Supports OAuth 2.1 credential storage via OS keychain, x402 micropayment protocol integration, and config-file references for local MCP servers.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work