Cline MCP Marketplace

Why it's ranked here

This is useful infrastructure for authors targeting Cline, with a low-friction submission form and explicit vetting criteria. Its value is narrow, however: the repository coordinates listings and approvals rather than implementing an independent marketplace client or MCP server.

What's good

The submission flow requires a repository link, square logo, installation test, and confirmation of public stability. Reviewers consider adoption, maintainer credibility, project maturity, documentation, maintenance, and security. Complex servers can supply extra agent-focused setup guidance for environment configuration or API keys.

Tradeoffs

Approval depends on qualitative review, including community traction and maintainer reputation, so acceptance is not purely specification-driven. Installation also relies on Cline interpreting project documentation correctly. The repository text gives no machine-readable listing format, local validation tool, automated security scan, or portable installer.

How to use it well

Use it when publishing a stable MCP server specifically for discovery and installation by Cline users. Write complete setup documentation, test installation from that documentation alone, and disclose special dependencies. Keep separate tooling for package distribution, security analysis, release automation, and support outside Cline.

Observed

License

MIT License

Submission interface

Structured GitHub issue form

Installation surface

One-click installation inside Cline, with Cline handling cloning, setup, and configuration

Required submission checks

Repository URL, logo, documentation-only installation test, and public stability confirmation

Documentation languages

English and Traditional Chinese

Repository structure

Documentation and GitHub issue configuration are shown; no application source or test directory appears in the supplied tree