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.

DimensionNetwork Sketcher (Local MCP)Local-first, AI-native MCP server for network design automationGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS59 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions9 / 2014 / 20
Maintenance14 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Teams using Cursor or Claude Code who want to drive network design directly through tool calls
  • Local single-user workflows that keep master files on the machine with no external communication
  • Network engineers who need Cisco-style L1/L2/L3 topology diagrams (SVG / PowerPoint), device tables, and AI Context files
  • Users willing to use a model with strong multi-step tool-calling ability (Claude Opus 4.7 or later recommended)
  • 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
  • Deployments needing HTTP/SSE transport or multi-user concurrency (stdio, single-user only)
  • Scenarios where the LLM client must directly view PPTX / SVG binary output (the user should open the generated SVG)
  • Environments that cannot run Python or install local dependencies
  • Network designs requiring IPv6 (IPv6 is not supported)
  • Needs for master file creation from PowerPoint sketches, GUI add/delete of VPNs, or Flow management (not offered in this edition)
  • 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
  • Read and write workspace directories under the user's home directory (set_workspace validates the path is under the home directory and confirms it is writable)
  • Create and read .nsm master files in the active workspace
  • Read a .xlsx file at a given path for import_master
  • Write generated SVG / PPTX diagrams, .xlsx files, and HTML device tables into the active workspace
  • Launch a local Python subprocess to execute Network Sketcher CLI commands
  • 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
  • run_commands batches LLM-generated CLI commands into a local subprocess, so wrong or unintended commands can modify the .nsm master (back up first or experiment with an empty master)
  • import_master and export_master_xlsx read and write files in the workspace; path mistakes or overwrites can affect existing files
  • Imported converter output is only a starting draft and may have data-quality issues requiring review
  • Diagram generation for large networks may take a long time
  • Weaker or older models may struggle to follow the layout / workflow rules embedded in the server instructions and AI Context (e.g. RULE 0 / 0.5 layout, RULE 3.5 multi-transport WAN waypoint design, the mandatory get_workspace_info to get_ai_context bootstrap)
  • 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 clientsCursor, Claude CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1115