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.

DimensionLogClaw MCP ServerConnect AI coding tools to LogClaw incidents, logs, and anomaly detectionsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS56 / 100 · C76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • SRE and development teams already running LogClaw or using its cloud service
  • Engineers who want incident and log data directly in Claude Code, Cursor, or Windsurf
  • 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 who do not use the LogClaw platform
  • Anyone without a valid LOGCLAW_API_KEY (lc_proj_ prefix)
  • 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 a valid LogClaw project API key (lc_proj_ prefix)
  • Network access to the LogClaw auth proxy endpoint (default https://ticket.logclaw.ai)
  • 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
  • API key leakage could expose project incident and log data; secure environment variables accordingly
  • Logs exposed to AI tools may contain sensitive operational information
  • Depends on remote endpoint availability; the self-hosted local stack runs single-tenant with AI RCA disabled by default
  • 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 Code, Cursor, WindsurfClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015