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 ServerGitHub MCP

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	GitHub MCPMCP100 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.	Repository, issue, pull-request, and code context Teams that can issue a narrowly scoped PAT or use the hosted OAuth flow Read-only GitHub investigation using restricted toolsets
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.	Git hosting outside GitHub Users unable to run Docker for the documented local configuration Workflows that need only a small amount of public repository context
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 restrict the token to the necessary repositories and scopes The agent must not receive private repository, issue, pull-request, or user data Your organization has not approved the OAuth app or PAT policy
Provenance
Provenance details	First-party MCP SAP · Publisher source ↗	First-party MCP GitHub · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Sep 22, 2026 Package: Not documented
Popularity evidence
GitHub stars	37 GitHub stars · checked 2026-10-20	33,158 GitHub stars · checked 2026-09-24T04:14:26.342000Z
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✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP
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.	Hosted service supports OAuth; local stdio uses GITHUB_PERSONAL_ACCESS_TOKEN. GitHub recommends minimum scopes, separate tokens, rotation, and environment-variable handling.
Cost	No separate MCP package fee is documented; underlying SAP BTP/Mobile Services usage follows the user's SAP entitlements.	The open-source server is MIT licensed. GitHub account, Copilot, Enterprise, Actions, API, or other product charges and limits may apply independently.
Permissions	The process can write MDK project files and invoke MDK/Cloud Foundry operations available to the logged-in developer environment.	Access follows the authenticated GitHub identity and granted OAuth/PAT permissions. The server supports tool allow-lists, read-only mode, repository-oriented toolsets, and lockdown mode; write tools remain possible unless read-only mode is enabled.
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.	Repository contents, issues, pull requests, users, actions, and other enabled GitHub API data may be returned to the MCP client. The local server passes requests to GitHub; the hosted server is operated by GitHub. Do not place PATs in committed 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.	The default local toolsets include repositories, issues, pull requests, users, and context; limiting toolsets reduces capability and context size. Local Docker keeps the MCP process local but still sends authorized requests to GitHub APIs. PAT setup is explicit and portable, while hosted OAuth is easier but relies on GitHub's remote MCP service.
Risk context	Tools can generate files, build, migrate, deploy projects, and fetch Mobile Services metadata. Deployment operations can affect shared SAP environments.	A broadly scoped token plus write-capable tools can alter repositories and collaboration records. Prefer fine-grained credentials, repository restriction, explicit toolsets, GITHUB_READ_ONLY=1, and lockdown mode where public-content prompt injection is a concern.
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 →