Update README.md: Add an open source cross-platform GUI desktop app

[aiqlcom]

Add an open source cross-platform GUI desktop application compatible with Linux, macOS, and Windows, enabling seamless interaction with MCP servers across dynamically selectable LLMs.

Description

This desktop application utilizes the MCP (Model Context Protocol) to seamlessly connect and interact with various Large Language Models (LLMs). Built on Electron, the app ensures full cross-platform compatibility, enabling smooth operation across different operating systems.

The primary objective of this project is to deliver a clean, minimalistic codebase that simplifies understanding the core principles of MCP. Additionally, it provides a quick and efficient way to test multiple servers and LLMs, making it an ideal tool for developers and researchers alike.

Motivation and Context

Key features of this application include:

• Cross-Platform Compatibility: Supports Linux, macOS, and Windows.

• Flexible Apache-2.0 License: Allows easy modification and building of your own desktop applications.

• Dynamic LLM Configuration: Compatible with all OpenAI SDK-supported LLMs, enabling quick testing of multiple backends through manual or preset configurations.

• Multi-Client Management: Configure and manage multiple clients to connect to multiple servers using MCP config.

• UI Adaptability: The UI can be directly extracted for web use, ensuring consistent ecosystem and interaction logic across web and desktop versions.

How Has This Been Tested?

Core Functionality Testing, including:

• Initialization, visualization, and functional invocation of multiple MCP clients

• Basic installation and packaging procedures

• Cross-platform packaging tests for: Windows 10, Ubuntu 22, and macOS Sequoia

• Multimodal support testing

• Agent capability testing: Currently limited by LLM capabilities, only Claude, ChatGPT, and Qwen meet basic tool call requirements

• Maintainability testing: Including basic console.log output and Chromium-based DevTools message interaction

Breaking Changes

The desktop application is compatible with the current MCP client configurations utilized by Claude.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[jspahrsummers]

Hi! I'm Claude. The lists in the README have now been alphabetized, so this entry should be inserted in alphabetical order. Please update your PR to place the GUI desktop app alphabetically in the community servers section. Additionally, please update your branch with the latest changes from main to resolve any merge conflicts.

[aiqlcom]

Hi! I'm Claude. The lists in the README have now been alphabetized, so this entry should be inserted in alphabetical order. Please update your PR to place the GUI desktop app alphabetically in the community servers section. Additionally, please update your branch with the latest changes from main to resolve any merge conflicts.

@jspahrsummers I've updated the PR according to your comments.

fixed