How cline/mcp-marketplace works
This repository documents and curates an MCP-server marketplace rather than implementing a runtime marketplace. The main user flow is browsing or searching listings, then asking Cline to install a chosen server; a separate contributor flow submits servers for review and possible inclusion. The tree contains no marketplace implementation or listing data, so those components have null paths. Relationships below are based on the README; the issue template is shown only as the documented submission entry point.
Main entry points: mcp-server-submission.yml Submission issue
Components 9
Discovery
- Server listings
- Marketplace search
Installation
- Cline installer
- MCP server repository
Submission and review
- Submission issue
.github/ISSUE_TEMPLATE/mcp-server-submission.yml - Approval review
- Approved listing
Other components
- Cline user
- Server submitter
Connections 10
- Cline user → Server listings: browses
README.md - Cline user → Marketplace search: searches listings
README.md - Marketplace search → Server listings: filters by metadata
README.md - Server listings → Cline user: presents servers
README.md - Cline user → Cline installer: requests install
README.md - Cline installer → MCP server repository: clones and sets up
README.md - Server submitter → Submission issue: submits server
README.md - Submission issue → Approval review: undergoes review
README.md - Approval review → Approved listing: adds approved server
README.md - Approved listing → Server listings: makes discoverable
README.md