Ext Ops Panel
Open dashboard
Comparison

Alfresco vs io.github.kontent-ai/mcp-server

Alfresco is an MCP server published by AlfrescoLabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.kontent-ai/mcp-server is an MCP server published by kontent-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceAlfrescoio.github.kontent-ai/mcp-server
Docker MCP Catalog Listed
Version: sha256:00fa4bcb0a4f
Forks (GitHub): 2
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.39.0
Downloads/month (npm): 1 072
Downloads/week (npm): 301
Forks (GitHub): 13
Stars (GitHub): 9
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

Alfresco vs io.github.kontent-ai/mcp-server
FactAlfrescoio.github.kontent-ai/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)6 (worse)9 (better)
Forks (GitHub) (differs)2 (worse)13 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (angelborroy/alfresco-mcp-server)On your machine (@kontent-ai/mcp-server)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/alfrescolabs/alfresco-mcp-servergithub.com/kontent-ai/mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Alfresco

In its own words, on Docker MCP Catalog:

A minimal Model Context Protocol (MCP) server for Alfresco providing tools via the Alfresco REST API.

io.github.kontent-ai/mcp-server

In its own words, on Official MCP Registry:

Connect to Kontent.ai to manage content, types, taxonomies, and workflows via natural language

How to run each

Alfresco As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio alfresco -- docker run -i --rm angelborroy/alfresco-mcp-server

io.github.kontent-ai/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "KONTENT_API_KEY=<YOUR_KONTENT_API_KEY>" --env "KONTENT_ENVIRONMENT_ID=<YOUR_KONTENT_ENVIRONMENT_ID>" --transport stdio io-github-kontent-ai-mcp-server -- npx -y @kontent-ai/mcp-server stdio

Requires: KONTENT_API_KEY (secret), KONTENT_ENVIRONMENT_ID

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

Tools each declares

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

Settings each asks for

Only Alfresco asks for

  • ALFRESCO_HOST

Only io.github.kontent-ai/mcp-server asks for

  • KONTENT_API_KEY (secret)
  • KONTENT_ENVIRONMENT_ID
  • PORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Alfresco · What it can do: io.github.kontent-ai/mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built