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.

DimensionSAP Docs MCP ServerA unified hybrid-search MCP server for SAP documentation, with no API key required.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS65 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • SAP developers working with SAPUI5, CAP, BTP, or ABAP
  • Teams that want SAP official and community docs searchable directly in their editor or AI assistant
  • Offline or restricted-network scenarios that need a local index
  • Developers tracking clean core compliance and SAP released object state
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • General documentation search outside the SAP technology stack
  • Scenarios requiring writes, modifications, or deployments to SAP systems (the server is read-only)
  • Enterprise support scenarios needing official SAP support or licensed credentials
  • Users requiring vendor-official maintenance guarantees
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Local runs need network access to clone documentation submodules and for optional online queries (SAP Help, SAP Community, Software Heroes)
  • Local builds require write access to the project directory (index database docs.sqlite, embedding model cache in dist/models, about 90 MB)
  • Docker offline runs can fully disable networking via --network none
  • The hosted endpoint requires no API key or login and is public read-only
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Online queries send search keywords to external sources (SAP Help, SAP Community, Software Heroes)
  • The local index and embedding model consume disk space (model is about 90 MB, build caches are larger)
  • Setup clones multiple SAP documentation repositories, which takes time and depends on network stability
  • The server is community-maintained and not an official SAP product, so docs and behavior may change with upstream
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude, Cursor, ChatGPTClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools90