Ext Ops Panel
Open dashboard
Comparison

io.github.SAP/mdk-mcp-server vs Textavia MCP

io.github.SAP/mdk-mcp-server is an MCP server published by SAP. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). Textavia MCP is an MCP server published by catorch. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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.SAP/mdk-mcp-serverTextavia MCP
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 39 812
Downloads/week (npm): 5 836
Forks (GitHub): 11
Stars (GitHub): 38
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 125
Downloads/week (npm): 18
Not marked · First seen
Claude Code: claude-plugins-official Listed
Version: 0.5.0
Forks (GitHub): 11
Stars (GitHub): 38
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.4.0
Forks (GitHub): 11
Stars (GitHub): 38
Not marked · First seen
Not listed

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.SAP/mdk-mcp-server vs Textavia MCP
Factio.github.SAP/mdk-mcp-serverTextavia MCP
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)38No figure on GitHub
Forks (GitHub) (differs)11No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@sap/mdk-mcp-server)On your machine (@textavia/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/sap/mdk-mcp-serverNot stated
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

io.github.SAP/mdk-mcp-server

In its own words, on Official MCP Registry:

Model Context Protocol (MCP) server for AI-assisted development of MDK applications.

Textavia MCP

In its own words, on Official MCP Registry:

Local-first MCP server for text, JSON, Base64, CSV, regex, and developer utilities.

How to run each

io.github.SAP/mdk-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mdk-mcp-server -- npx -y @sap/mdk-mcp-server

Textavia MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio textavia-mcp -- npx -y @textavia/mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.SAP/mdk-mcp-server · What it can do: Textavia MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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