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.

DimensionGalaxy MCP ServerMCP server for the Galaxy bioinformatics platformGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS61 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Bioinformatics researchers who want AI assistants to operate the Galaxy platform
  • Galaxy instance administrators and regular Galaxy users
  • Teams automating analysis workflows
  • 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 not on the Galaxy platform
  • Environments without a Galaxy URL and API key
  • General-purpose bioinformatics outside Galaxy
  • 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
  • Requires the target Galaxy instance URL (GALAXY_URL, required)
  • Requires a Galaxy API key (GALAXY_API_KEY, required and secret; may be omitted when using OAuth)
  • OAuth mode requires a session secret (GALAXY_MCP_SESSION_SECRET) and public URL (GALAXY_MCP_PUBLIC_URL)
  • 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
  • The API key is a sensitive credential; leakage grants others access to your Galaxy account and analyses
  • Tools and workflows executed by the AI consume Galaxy compute resources
  • Remote HTTP deployment exposes a network port and requires careful OAuth and session-secret configuration
  • 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 DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015