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.

DimensionGeneXus MCP ServerRead, edit, and analyze GeneXus 18 knowledge base objects via MCP.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS60 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers and teams using GeneXus 18
  • AI tool users who want to interact with the knowledge base via natural language
  • 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
  • Users without GeneXus
  • Cross-platform needs (Windows only)
  • Users expecting no local installation
  • 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
  • Read/write local file system (KB files)
  • Execute build/deploy processes
  • Network access for certain features
  • 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
  • Misusing edit tools could damage KB, but rollback is available
  • Build processes may incur performance overhead
  • Requires granting sufficient execution permissions
  • 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, Cursor, Antigravity, Gemini CLI, OpenCode, Codex, VS Code, VS Code InsidersClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools470