@cybertheory/mcpkit - npm Package Compare versions

Comparing version

0.3.0

0.3.1

+1

-1

package.json

		{
		"name": "@cybertheory/mcpkit",
		"version": "0.3.0",
		"version": "0.3.1",
		"description": "Lightweight UI console to detect MCP-capable coding agents and install MCP servers",
		@@ -5,0 +5,0 @@ "keywords": [

+41

-11

README.md

		# MCP Kit

		A lightweight UI console to detect MCP-capable agents and install MCP servers. Easily manage Model Context Protocol integrations for Cursor, Windsurf, Claude Desktop, Continue, Aider, Cline, Neovim, Emacs, JetBrains IDEs and other MCP-capable assistants.
		A lightweight UI console client for the [official MCP Registry](https://github.com/modelcontextprotocol/registry) that detects MCP-capable agents and installs MCP servers. Easily manage Model Context Protocol integrations for Cursor, Windsurf, Claude Desktop, Continue, Aider, Cline, Neovim, Emacs, JetBrains IDEs and other MCP-capable assistants.

		> 🌐 Official Registry Client: MCP Kit is built as a client for the official MCP Registry, following the specifications and standards defined by the Model Context Protocol community. All server data comes directly from [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io).

		![MCP Kit Screenshot](assets/image.png)
		@@ -51,6 +53,6 @@

		- Official Registry Integration: Built as a client for the [official MCP Registry](https://github.com/modelcontextprotocol/registry), ensuring all server data comes from the authoritative source
		- Registry-First Architecture: All installations use official registry metadata including npm packages, versions, and environment variables
		- Auto-Detection: Automatically finds Cursor, Windsurf, Claude Desktop, Continue, Aider, Cline, Neovim, Emacs, JetBrains IDEs and other MCP-capable agents
		- Official Registry Integration: Direct integration with the official MCP registry (registry.modelcontextprotocol.io) for authentic server data
		- One-Click Install: Install MCP servers directly from registry with proper environment variable configuration
		- Registry-First: All installations use official registry metadata including npm packages, versions, and environment variables
		- OAuth Support: Handle authentication flows for services like GitHub
		@@ -202,13 +204,24 @@ - Offline Fallback: Works even when registry is unavailable using cached data

		## 🌐 Registry
		## 🌐 Official MCP Registry Integration

		MCP Kit uses the official MCP registry (registry.modelcontextprotocol.io) as the primary source for all server data. This ensures:
		MCP Kit is designed as a client for the [official MCP Registry](https://github.com/modelcontextprotocol/registry), following the specifications and standards defined by the Model Context Protocol community. This ensures:

		- ✅ Authentic Data: All server information comes directly from the official registry
		- ✅ Latest Versions: Automatic updates with the most recent server versions
		- ✅ Proper Metadata: Complete package information, environment variables, and installation commands
		- ✅ Verified Sources: Only officially registered and verified MCP servers
		### ✅ Registry Compliance
		- Authentic Data: All server information comes directly from the official registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io)
		- Latest Versions: Automatic updates with the most recent server versions from the registry
		- Proper Metadata: Complete package information, environment variables, and installation commands as defined by the registry
		- Verified Sources: Only officially registered and verified MCP servers are available for installation

		The registry is automatically updated every 30 minutes, and you can manually refresh using the "Refresh Registry" button in the UI. If the official registry is unavailable, MCP Kit falls back to cached data to ensure continued operation.
		### 🔄 Registry Synchronization
		- Real-time Updates: Registry data is automatically updated every 30 minutes
		- Manual Refresh: Use the "Refresh Registry" button in the UI to get the latest data
		- Offline Support: Cached data ensures continued operation when the registry is unavailable
		- API Compliance: Follows the official MCP Registry API specifications for data retrieval and server management

		### 🏗️ Architecture Benefits
		- Standards Compliance: Built according to MCP Registry specifications
		- Community Alignment: Integrates seamlessly with the broader MCP ecosystem
		- Future-Proof: Automatically adapts to registry API changes and improvements
		- Trust & Security: Users can trust that all servers come from the official, verified registry

		## 🚀 Publishing
		@@ -229,2 +242,5 @@

		We welcome contributions to MCP Kit! As a client for the official MCP Registry, we follow the specifications and standards defined by the Model Context Protocol community.

		### Quick Start
		1. Fork the repository
		@@ -235,2 +251,16 @@ 2. Create a feature branch

		### Detailed Guidelines
		See our [CONTRIBUTING.md](CONTRIBUTING.md) for comprehensive contribution guidelines, including:
		- Development setup and project structure
		- Code style guidelines and testing requirements
		- MCP Registry integration standards
		- Review process and community guidelines

		### Registry Compliance
		When contributing, please ensure:
		- All changes maintain compatibility with the official MCP Registry API
		- Server installations follow registry specifications
		- Error handling includes proper fallback mechanisms
		- Documentation reflects registry integration features

		## 📄 License
		@@ -248,2 +278,2 @@

		Made with ❤️ for the MCP community
		Made with ❤️ for the MCP community \| Built for the [Official MCP Registry](https://github.com/modelcontextprotocol/registry)

@cybertheory/mcpkit - npm Package Compare versions

Fixed alerts

Improved metrics