Submission And Contribution Guidelines For New Remote Mcp Servers

via “monorepo-based mcp server development framework with shared infrastructure”

Manage Cloudflare Workers, KV, R2, and DNS via MCP.

Unique: Monorepo with shared @repo/mcp-common, @repo/mcp-observability, and @repo/eval-tools packages eliminates authentication and observability boilerplate across 15+ servers; Turbo orchestration enables parallel builds and incremental deployments

vs others: More maintainable than standalone MCP servers because shared packages enforce consistency, and faster to develop because authentication and observability are pre-built

via “1.1 mcp protocol and architecture”

Official MCP reference server — current time and timezone conversion tools for agents.

via “mcp server contribution guidelines and standardization”

A collection of MCP servers.

Unique: Establishes community contribution standards for MCP server registry with support for multiple languages (Chinese, Japanese, Korean), enabling global contributors to add servers while maintaining consistent metadata formatting and category assignment across 200+ entries.

vs others: More inclusive than English-only registries; internationalization support enables non-English speaking developers to contribute and discover servers, whereas most open-source registries default to English-only documentation.

via “mcp server lifecycle management and configuration”

MCP server for Apple Developer Documentation - Search iOS/macOS/SwiftUI/UIKit docs, WWDC videos, Swift/Objective-C APIs & code examples in Claude, Cursor & AI assistants

Unique: Implements full MCP server lifecycle (initialization, configuration, tool registry setup, graceful shutdown) with support for multiple MCP clients (Claude Desktop, Cursor, VS Code, Windsurf, Zed, Cline) through standard MCP protocol

vs others: More flexible than hardcoded MCP servers because it supports configuration-driven setup, and more robust than simple scripts because it handles protocol handshake and error recovery

via “community contribution guidelines and standardized submission process”

Awesome MCP Servers - A curated list of Model Context Protocol servers

Unique: Establishes explicit community governance with standardized submission templates and review criteria, rather than accepting arbitrary contributions — creating a curated registry where quality and documentation standards are enforced rather than a free-for-all listing

vs others: More structured than typical awesome-* repositories because MCP's protocol standardization enables meaningful quality criteria (compatibility testing, configuration validation) rather than just subjective 'awesomeness' judgments

via “github pr-based community server contribution workflow”

Discover Exceptional MCP Servers

Unique: Uses GitHub's native PR workflow as the contribution mechanism, with servers.json as the single source of truth that gets updated through merged PRs, rather than a separate contribution form or API endpoint

vs others: More transparent and auditable than API-based submissions because the full history is visible in Git, but slower than automated systems because human review is required before each server goes live

via “mcp server publishing and contribution workflow”

** MCP Marketplace is a small Web UX plugin to integrate with AI applications, Support various MCP Server API Endpoint (e.g pulsemcp.com/deepnlp.org and more). Allowing user to browse, paginate and select various MCP servers by different categories. [Pypi](https://pypi.org/project/mcp-marketplace) |

Unique: Provides structured publishing workflow for MCP server developers including schema contribution guidelines, configuration templates, and integration testing documentation, enabling community-maintained servers to be discoverable in centralized marketplace

vs others: Offers guided publishing workflow with standardized schema and configuration requirements, whereas ad-hoc publishing approaches lack consistency and make tool discovery difficult

via “dynamic mcp server configuration with local and remote support”

** - Experimental agent prototype demonstrating programmatic MCP tool composition, progressive tool discovery, state persistence, and skill building through TypeScript code execution by **[Adam Jones](https://github.com/domdomegg)**

Unique: Supports both local (stdio) and remote (HTTP/SSE) MCP server connections through unified configuration, enabling flexible deployment patterns without code changes

vs others: Enables environment-specific server configurations through environment variables, unlike hardcoded server lists

via “community contribution guidelines and registry maintenance”

** (**[website](https://glama.ai/mcp/servers)**) - A curated list of MCP servers by **[Frank Fiegel](https://github.com/punkpeye)**

Unique: Establishes clear community contribution guidelines and registry maintenance processes that enable the registry to scale with community submissions while maintaining consistency and quality, treating the registry as a collaborative resource rather than a static list

vs others: More structured than ad-hoc community lists; provides clear contribution pathways and review criteria that encourage participation while maintaining registry quality

via “mcp-server-hosting-and-deployment”

Return any inbound message duplicated to enhance message processing workflows. Easily integrate with your applications to echo inputs twice for testing or demonstration purposes. Deploy seamlessly with Smithery for scalable and session-based MCP server hosting.

Unique: Smithery provides managed MCP server hosting with automatic session isolation and scaling, whereas alternatives like Anthropic's MCP reference implementation require developers to self-host on their own infrastructure. This eliminates the operational burden of managing server uptime, scaling, and connection routing.

vs others: Faster to deploy and share than self-hosted MCP servers because Smithery handles infrastructure provisioning and scaling automatically, whereas self-hosting requires Docker, cloud account setup, and ongoing maintenance.

** - A curated list of **remote** MCP servers, including their authentication support by **[JAW9C](https://github.com/jaw9c)**

Unique: Enforces quality criteria and legitimacy verification as part of the contribution process, ensuring that only vetted remote servers enter the directory. Provides structured submission format and pull request process to enable community curation while maintaining standards.

vs others: More rigorous than open registries because it requires manual review and quality verification before inclusion, preventing spam and unvetted servers. Provides clear submission guidelines, reducing friction for contributors while maintaining directory quality.

via “mcp server implementation pattern documentation and guidelines”

** (**[website](https://mcp-servers-hub-website.pages.dev/)**) - A curated list of MCP servers by **[apappascs](https://github.com/apappascs)**

Unique: Documents MCP server implementation architectures and development guidelines within the hub, providing pattern examples and contribution guidance for developers building new servers. This contextualizes the catalog within a broader ecosystem of server development practices and conventions.

vs others: Combines server discovery with implementation guidance and contribution workflows, unlike generic awesome-lists that only catalog existing projects; helps developers understand not just what servers exist, but how to build compatible new ones.

via “open-source reference implementation and community contribution”

The one and only MCP Server for dads jokes.

Unique: Positioned as an open-source reference implementation for MCP servers, making architectural decisions and code patterns transparent and reusable. Enables community-driven improvements and forks.

vs others: More transparent and learnable than closed-source MCP servers — developers can inspect implementation details, understand design rationale, and adapt patterns for their own servers.

via “remote-mcp-server-aggregation-and-routing”

** - MCP of MCPs. Automatic discovery and configure MCP servers on your local machine. Fully REMOTE! Just use [https://mcp.1mcpserver.com/mcp/](https://mcp.1mcpserver.com/mcp/)

Unique: Implements a transparent HTTP-to-MCP protocol bridge that preserves MCP semantics (tool calling, resource access, sampling) while exposing them through a standard HTTP endpoint, enabling cloud-based AI agents to interact with local servers without requiring MCP protocol support in the client

vs others: More flexible than individual server tunneling (ngrok, SSH tunnels) because it provides semantic routing and aggregation at the MCP protocol level; simpler than building custom API gateways because it understands MCP tool/resource structure natively

via “mcp server lifecycle management (add, remove, update)”

** - Simple Web UI to install and manage MCP servers for Claude Desktop by **[Zue](https://github.com/zueai)**

Unique: Implements server lifecycle management through a template-driven UI rather than direct JSON editing, providing validation and error feedback at each step. The architecture maintains an in-memory representation of servers that can be modified and validated before persisting to disk, preventing invalid configurations from being written to the Claude Desktop config file.

vs others: More user-friendly than manual JSON editing or CLI commands, but less powerful than programmatic APIs for bulk operations or conditional configuration logic

via “web portal submission and validation workflow”

** (**[website](https://mcpservers.org)**) - A curated list of MCP servers by **[wong2](https://github.com/wong2)**

Unique: Decouples submission interface from Git workflow by using an external web portal that validates and deduplicates submissions before they reach the repository, eliminating the need for maintainers to manually review and reject invalid PRs — a design pattern that trades transparency for operational efficiency.

vs others: More scalable than direct GitHub PRs because it prevents invalid submissions from cluttering the repository and provides pre-validation, but less transparent than community-driven awesome-lists because submission criteria and approval process are not publicly visible.

via “remote mcp server provisioning and connection management”

MCP of MCPs. A central hub for MCP servers. Helps you discover available MCP servers and learn how to install and use them. REMOTE! Use the url [https://mcp.pfvc.io/mcp/](https://mcp.pfvc.io/mcp/) to add the server. **Remember the final backslash\*\*.

Unique: Implements MCP as a remote-first service with no local installation requirement, using a hosted endpoint that handles all server infrastructure, whereas typical MCP servers require local deployment and dependency management

vs others: Eliminates setup friction compared to self-hosted MCP servers, making it accessible to developers who want discovery without infrastructure overhead

via “mcp server lifecycle management and protocol handshake”

MCP-compatible server tool for filesystem access from https://github.com/adisuryanathan/modelcontextprotocol-servers.git

Unique: Implements complete MCP server lifecycle as a Node.js module, handling protocol handshake and state management. Exposes filesystem capabilities through standardized MCP capability declarations.

vs others: More complete than minimal MCP implementations because it handles full lifecycle; more maintainable than custom protocol implementations because it follows MCP specification.

via “client-specific mcp server setup guide aggregation”

** - A growing directory of high-quality MCP servers with clear setup guides for a variety of MCP clients. Built by the team behind the **[Highlight MCP client](https://highlightai.com/)**

Unique: Curates setup guides across multiple MCP clients in a single directory, mapping each server to client-specific configuration patterns. Rather than requiring users to search each server's README for client-specific instructions, MCPServers.com pre-indexes and links to the correct setup path for each client combination.

vs others: Reduces setup friction compared to reading individual server READMEs because it provides client-specific navigation and aggregates setup instructions in one place, whereas users typically must visit each server's GitHub repository and manually search for their client's configuration syntax.

via “mcp server publishing and distribution workflow”

** - An open registry for finding, installing, and building with MCP servers by **[opentoolsteam](https://github.com/opentoolsteam)**

Unique: Implements a curated registry submission workflow with MCP-specific validation (protocol compliance testing, capability schema validation, context window requirement verification) rather than open-upload-only distribution like npm or PyPI

vs others: More discoverable than publishing to generic package managers alone, with MCP-specific quality gates that ensure ecosystem reliability, though more restrictive than fully open registries