Clients & CLI

A whole-word text match over name, one-line summary, original description and field tags (cli / command line). It is a text match, not an official label, and nothing was confirmed by hand: a project may say CLI and still be a library, and a server that ships a CLI without the word in its description will not appear. The count is recomputed from the database on every rebuild.

Because the database has no such field and no source provides one. Filling that matrix would mean guessing, and a guessed cell is worse than an empty one. The client half lists how each client connects generally, with a link to its own documentation.

Each row prints the date we checked it: 2026-10-20, opened one by one, HTTP 200, with the stdio / HTTP connection described in the document itself. Documentation changes; the link is the current source of truth.

By evidence, not by name: whether the official MCP Registry records a remote endpoint for the repository, whether the entry URL is itself an endpoint, and whether the install command is a command or a URL. What we cannot establish we leave unlabelled, and the coverage numbers are printed on the Remote servers page.

Open its detail page: source link, when we last saw it, and a confirmed install command where one exists (when it could not be confirmed, the page says so rather than printing a command that will fail).