Ext Ops Panel
Open dashboard
Comparison

io.github.kubeshop/testkube-mcp vs io.github.pnp/cli-microsoft365-mcp-server

io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.pnp/cli-microsoft365-mcp-server is an MCP server published by pnp. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.kubeshop/testkube-mcpio.github.pnp/cli-microsoft365-mcp-server
Official MCP Registry Listed
Version: 2.14.2
Forks (GitHub): 180
Stars (GitHub): 1 676
Not marked · First seen
Listed
Version: 0.1.22
Downloads/month (npm): 2 305
Downloads/week (npm): 488
Forks (GitHub): 29
Stars (GitHub): 135
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:43aa88f2d416
Forks (GitHub): 180
Pulls (Docker Hub): 34 070
Stars (Docker Hub): 0
Stars (GitHub): 1 676
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 0.1.25
Downloads/month (npm): 2 305
Downloads/week (npm): 488
Forks (GitHub): 29
Stars (GitHub): 135
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

io.github.kubeshop/testkube-mcp vs io.github.pnp/cli-microsoft365-mcp-server
Factio.github.kubeshop/testkube-mcpio.github.pnp/cli-microsoft365-mcp-server
Marketplaces that list it22
Stars (GitHub) (differs)1 676 (better)135 (worse)
Pulls (Docker Hub) (differs)34 070No figure on Docker Hub
Forks (GitHub) (differs)180 (better)29 (worse)
Last release (differs)2026-10-19 (better)2026-10-13 (worse)
Where it runs (differs)Remote server or your machineOn your machine (@pnp/cli-microsoft365-mcp-server)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)28Not published
Environment variables it asks for (differs)9, secrets among them: 1Not published
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/kubeshop/testkubegithub.com/pnp/cli-microsoft365-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 7 days ago, requires a keyno remote endpoint we check

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

io.github.kubeshop/testkube-mcp

In its own words, on Official MCP Registry:

MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants

io.github.pnp/cli-microsoft365-mcp-server

In its own words, on Official MCP Registry:

MCP server for CLI for Microsoft 365 to manage your tenant using natural language

How to run each

io.github.kubeshop/testkube-mcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkube

Requires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)

io.github.pnp/cli-microsoft365-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio cli-microsoft365-mcp-server -- npx -y @pnp/cli-microsoft365-mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.pnp/cli-microsoft365-mcp-server publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.pnp/cli-microsoft365-mcp-server publish no settings it asks for, so we do not compare settings.

What it can do: io.github.kubeshop/testkube-mcp · What it can do: io.github.pnp/cli-microsoft365-mcp-server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). 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