M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCP Abap AdtMCP server for SAP ABAP ADT: full CRUD for RAP and classic ABAP, supporting SAP BTP ABAP Cloud and On-Premise ECC/S/4HANA with JWT/XSUAA and service-key auth.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS61 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • ABAP developers and architects
  • RAP developers
  • Team leads and tech leads needing fast repository visibility
  • Teams building RAG/agent workflows for SAP landscapes
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users without SAP systems
  • Users who require read-only access (this server provides full CRUD)
  • Users relying on unsupported authentication methods
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires access to the SAP system URL (SAP_URL)
  • Requires authentication credentials: JWT token (XSUAA) or basic auth username/password
  • Requires an ABAP client number (SAP_CLIENT)
  • Requires transport request privileges for on-premise systems (SAP_MASTER_SYSTEM, SAP_RESPONSIBLE)
  • Can create, read, update, and delete ABAP objects, so needs appropriate permissions in the ABAP system
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • AI agents may unintentionally modify or delete ABAP objects if given overly broad permissions
  • Exposed credentials (passwords, JWT tokens) may be leaked if not handled securely
  • Frequent access to SAP systems could cause performance or lock issues
  • Code generation quality may not meet production standards and requires human review
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools6515