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 platformGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS54 / 100 · D76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions11 / 2014 / 20
Maintenance15 / 2018 / 20
Documentation9 / 2017 / 20
Setup experience11 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users without a running Kaneo instance
  • Anyone needing integration with other project management platforms (Jira, Linear, etc.) — this server only targets Kaneo
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Desktop, CursorClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015