Ext Ops Panel
Open dashboard
Comparison

connector-namespaces vs io.github.bea-technology/roxyon

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). io.github.bea-technology/roxyon is an MCP server published by bea-technology. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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

Where each is published
Marketplaceconnector-namespacesio.github.bea-technology/roxyon
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: 0.4.0
Downloads/month (npm): 452
Downloads/week (npm): 63
Forks (GitHub): 0
Stars (GitHub): 0
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

connector-namespaces vs io.github.bea-technology/roxyon
Factconnector-namespacesio.github.bea-technology/roxyon
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)20 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)Not published4
Licence (differs)MITNot stated
Repository (differs)github.com/azure/connectorsgithub.com/bea-technology/roxyon-devtools
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Copilot CLI: github/awesome-copilot:

Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.

io.github.bea-technology/roxyon

In its own words, on Official MCP Registry:

Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

How to run each

connector-namespaces

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.bea-technology/roxyon As a remote MCP server

Claude Code
claude mcp add --transport http roxyon https://mcp.roxyon.com/mcp

Requires: ROXYON_TOKEN (secret)

Commands 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

The marketplaces of connector-namespaces publish no settings it asks for, so we do not compare settings.

What it can do: connector-namespaces · What it can do: io.github.bea-technology/roxyon · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built