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.

DimensionOPC UA MCP ServerOperate OPC UA through MCP for AI assistants.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS41 / 100 · D76 / 100 · B
Reliability7 / 2013 / 20
Security and permissions6 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation8 / 2017 / 20
Setup experience7 / 2014 / 20
Best for
  • OPC UA integration in industrial control, manufacturing, energy, and IoT systems
  • Developers who need AI assistants to access OPC UA client operations
  • Teams building OPC UA tools or applications on .NET
  • 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
  • Applications that do not use OPC UA
  • Deployments requiring documented tool identifiers or client configuration not present in the source
  • Environments requiring transport, authentication, or authorization details that the source does not specify
  • 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 access to the target OPC UA server
  • Read/write, method-call, and subscription operations require the corresponding permissions granted by the target OPC UA server; the precise permission model is not specified
  • 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
  • Writing values or calling methods may change industrial-system or device state
  • Subscriptions and diagnostics may maintain connections or consume additional resources
  • The source does not specify authentication, authorization, or transport configuration; verify the target environment's security requirements before deployment
  • Repository metadata is NOASSERTION, while the project README and server manifest state MIT; confirm the applicable license before adoption
  • 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, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015