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.

DimensionARC-1An enterprise MCP server for SAP ABAP systems.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS67 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions16 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Organizations seeking governed AI-assisted SAP ABAP development
  • Local or BTP deployments using the SAP ADT REST API
  • Teams that want read-only defaults with explicitly controlled write capabilities
  • 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-purpose business-data extraction
  • Production use without SAP authorization, credential, and security review
  • Users who require free SQL, table previews, or write operations to be enabled by default
  • 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
  • Requires SAP_URL, SAP_USER, and SAP_PASSWORD
  • SAP_CLIENT and SAP_LANGUAGE are optional and have defaults
  • Writing ABAP objects requires explicit SAP_ALLOW_WRITES enablement
  • Table data preview and free SQL require separate explicit environment variables
  • SAP-native authorization still governs relevant SAP operations
  • 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
  • SAP_PASSWORD is a secret credential and must be protected
  • Enabling writes can create, update, or delete ABAP objects
  • Enabling table previews can expose application data
  • Enabling free SQL can execute ad-hoc ABAP SQL
  • SAP_INSECURE skips TLS certificate verification
  • SAP API Policy, SAP agreements, and organizational data-governance requirements should be reviewed before production use
  • 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 Desktop, Claude Code, GitHub Copilot, Copilot Studio, Joule StudioClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools120