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.

DimensionKaneoOfficial MCP server for the Kaneo project management platformMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Teams already self-hosting or using Kaneo Cloud who want AI-client-driven task management
  • Developers preferring a lightweight, open-source project management tool over Jira/Linear
  • 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 a running Kaneo instance
  • Anyone needing integration with other project management platforms (Jira, Linear, etc.) — this server only targets Kaneo
  • 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
  • Network access to the configured KANEO_API_URL
  • Valid Kaneo credentials (API key or interactive device-authorization login)
  • Per the manifest description, the ability to manage (create/modify) tasks, projects, and labels
  • 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
  • KANEO_API_KEY is a sensitive credential; if mishandled it could allow reading or modifying data in the connected Kaneo instance
  • The manifest does not enumerate the specific tools/functions exposed, so the exact operation scope should be verified before granting broad write access
  • If pointed at a self-hosted instance, that instance's own security posture (e.g. AUTH_SECRET, database access) also affects overall risk
  • 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, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00