How to submit an MCP server to Cline Marketplace

Cline's marketplace is built from one JSON file per entry. You add registry/mcps/<slug>/entry.json to the cline/marketplace repository in a pull request, a check validates it, and merging publishes it to the catalog Cline clients read^[2]. An older repository takes submissions as issues instead, and still does.

entry.json, field by field

1 Oct 2026^[3][1]

{
  "$schema": "../../../schemas/mcp.schema.json",
  "id": "weather",
  "type": "mcp",
  "name": "Weather",
  "tagline": "Forecasts and alerts for any city",
  "description": "A remote MCP server that returns forecasts and severe-weather alerts.",
  "repo": "https://github.com/example-user/weather-mcp",
  "tags": ["data"],
  "license": "MIT",
  "verified": false,
  "install": {
    "args": ["weather", "--transport", "http", "https://weather.example.com/mcp"]
  }
}

The args differ by kind of server: a remote one with OAuth is ["name", "--transport", "http", "https://host/mcp"], and a local one is ["name", "--", "npx", "-y", "some-mcp-server"]^[1].

Opening the pull request

1. Create the folder and file, named by the slug.
2. Optionally put icon.svg or icon.png beside it and set "icon": "./icon.svg".
3. Run npm run validate; CI runs the same check on the pull request.
4. Open the pull request, and leave verified as false, since that mark is the Cline team's to give.

What fails validation

• A tag that is not in the list. The build fails on an unknown tag. If your category is missing, add it to tags.json in the same pull request^[2].
• A repeated id. An early pull request renamed an entry's id to linear-mcp to resolve a duplicate^[4].
• Slug and id that differ. The slug must equal the id^[1].
• A tagline over 120 characters.^[3]

The older route: an issue

cline/mcp-marketplace asks for a new issue with a repository URL, a 400 by 400 PNG logo and the reason for adding the server, and for you to have tested that Cline can set it up from your README or an optional llms-install.md^[7]. The repository's last commit is from June 2025, yet issues were still being opened and closed on 1 Oct 2026, and one was closed by its author with a note pointing to a pull request in the new repository^[8]. I found no page that says one repository replaces the other.

By hand

There is nothing here to automate away: it is a folder, a file and one command. The same server can sit in several directories, so see also the official registry.

Current status, 1 Oct 2026

On 2 Oct 2026 the new repository had 126 open pull requests and 2 open issues^[5]. Its merged pull requests number eight, all opened by the same account, and the newest was merged on 18 Sept 2026^[6]. The older repository had 2,382 open issues when I counted on 1 Oct 2026^[8].