connector-namespaces vs pracht dev-mcp
connector-namespaces is a plugin bundle for AI coding tools published by Azure. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). pracht dev-mcp is an MCP server published by JoviDeCroock. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  connector-namespaces |  pracht dev-mcp |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.2.0 Forks (GitHub): 7 Stars (GitHub): 20 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.16.1 Downloads/month (npm): 1 298 Downloads/week (npm): 827 Forks (GitHub): 5 Stars (GitHub): 99 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | connector-namespaces | pracht dev-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 20 (worse) | 99 (better) |
| Forks (GitHub) (differs) | 7 (better) | 5 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@pracht/cli) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/azure/connectors | github.com/jovidecroock/pracht |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
connector-namespaces
Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.
pracht dev-mcp
Inspect, verify, diff, and scaffold a pracht app's routes, API, and capabilities from its app graph.
How to run each
connector-namespaces
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
pracht dev-mcp As a local MCP server: npm package
claude mcp add --transport stdio pracht -- npx -y @pracht/cli dev-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: connector-namespaces · What it can do: pracht dev-mcp · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.