Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

SAP MDK MCP ServerDocker MCP Gateway

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	SAP MDK MCP ServerShortlist candidate	Docker MCP GatewayMCP100 Recommended
Task fit
Best for	Build and manage SAP Mobile Development Kit applications with coding agents Build and manage SAP Mobile Development Kit applications with coding agents.	Running multiple MCP servers behind one stdio connection Isolating catalog MCP servers in containers with restricted privileges and resources Centralizing server profiles, secrets, OAuth, logs, and call traces
Not ideal for	Several tools write files, build/deploy projects, or access SAP Mobile Services. The metadata-fetch tool requires Cloud Foundry authentication. Telemetry is enabled by default but can be disabled with SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY=true.	Users who need only one simple remote MCP endpoint Hosts where Docker Desktop or Docker Engine cannot run
Avoid when	Several tools write files, build/deploy projects, or access SAP Mobile Services. The metadata-fetch tool requires Cloud Foundry authentication. Telemetry is enabled by default but can be disabled with SAP_UX_FIORI_TOOLS_DISABLE_TELEMETRY=true.	You cannot review every downstream MCP server and profile permission The agent must not be able to discover or add tools dynamically Container isolation is being treated as protection from an over-privileged downstream credential
Provenance
Provenance details	First-party MCP SAP · Publisher source ↗	First-party MCP Docker · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Sep 23, 2026 Package: Not documented
Popularity evidence
GitHub stars	37 GitHub stars · checked 2026-10-20	1,581 GitHub stars · checked 2026-09-24T04:14:26.324000Z
Package downloads / 30 days	37,387 package downloads / 30 days · checked 2026-10-20	No reliable download data
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	The local stdio MCP itself does not require an MCP credential. Cloud Foundry authentication is required for Mobile Services metadata/deployment-related operations.	The gateway handles downstream server credentials and OAuth flows. The client connects locally over stdio by running `docker mcp gateway run`, optionally with a named profile.
Cost	No separate MCP package fee is documented; underlying SAP BTP/Mobile Services usage follows the user's SAP entitlements.	The open-source gateway documents no standalone usage fee. Docker Desktop licensing, Docker AI Governance invite-only features, container infrastructure, downstream MCP services, and AI-client charges may apply.
Permissions	The process can write MDK project files and invoke MDK/Cloud Foundry operations available to the logged-in developer environment.	The gateway exposes the servers and tools included in the selected profile. It starts catalog servers in containers with restricted privileges, network access, and resource usage, injects configured secrets, and can support OAuth. Dynamic MCP can additionally expose tools that discover, add, configure, remove, and execute servers during a session.
Data handling	Project files are processed locally. SAP states that non-personally-identifiable telemetry is collected by default and can be disabled via SAP UX telemetry settings/environment variables.	Tool requests and results pass through the local gateway to downstream MCP containers or remote services. Docker documents built-in logging and call tracing. Credentials are managed and injected by the gateway; downstream servers can still receive data and reach networks allowed by their configuration.
Limitations
Tradeoffs	Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.	Gateway isolation improves lifecycle and credential management but adds Docker runtime complexity and local resource use. The MCP Toolkit is documented as Beta, and Dynamic MCP is experimental. The gateway reduces direct host privileges, but network access and injected credentials still let downstream servers affect external systems.
Risk context	Tools can generate files, build, migrate, deploy projects, and fetch Mobile Services metadata. Deployment operations can affect shared SAP environments.	Gateway safety is only as strong as the selected profile, catalog provenance, tool filters, network policy, and downstream credentials. Disable experimental Dynamic MCP unless required, use narrow profiles, verify signatures where available, inspect traces, and treat each downstream server as a separate trust decision. This review does not claim MCP100 execution testing.
Evidence date
Editorial review	2026-10-19	2026-07-24
Candidate evidence	2026-10-20	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →