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.

DimensionHyperChatA local AI agent platform where configuration is code and tools come in through MCPMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS39 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Developers who want AI configuration stored locally and managed in Git
  • Users who need to reuse a personal agent across projects while keeping per-project context
  • Users who want agents to act on local resources such as the file system through MCP
  • Engineering teams that need a command-line entry point for automation
  • 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 who just want a hosted, zero-configuration cloud chat service
  • Users who require official commercial support or SLAs from the project maintainers
  • Users looking for a ready-made MCP tool list and client setup config, which the README does not provide
  • 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 file system read/write: the README states agents can operate on the local file system directly through the MCP protocol
  • Reading the project's .hyperchat/ configuration, agent memory, and chat logs
  • Reading environment variables and .env files (API keys, service port, Web access password)
  • Starting a local Web service that listens on a port (default 16100)
  • Calling external LLM provider API endpoints
  • 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
  • Once an agent is granted file-system or terminal MCP tools, it may modify local files, possibly without confirmation; the isConfirmCallTool setting in agent.yaml affects whether calls are confirmed
  • Configuration, agent memory, and chat logs are stored as plain local files, so committing them to Git or sharing the directory can leak sensitive information
  • Credentials such as API keys live in environment variables or .env files and can be committed by mistake or read by other local processes
  • If HYPERCHAT_WEB_PASSWORD is not set, the local Web service may be reachable by other processes or machines on the same network
  • Custom command templates send the referenced @ file contents to the configured LLM provider
  • The README states the project is for learning and exchange only and describes no security guarantees or audit mechanisms
  • 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 Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00