Skip to main content
Glama
magicsword-mcp

magicsword-mcp

Official

Related Servers

Alternatives to magicsword-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code, Claude Desktop, and Cursor to list hosts, read metrics, inspect containers, follow logs, and, when permitted, run commands, restart containers, manage authorized_keys, and edit host lists under per-host policy, Touch ID-backed credentials, deny-lists, rate limits, and an audit log.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Desktop, Claude Code, and other MCP clients to manage firewall rules, VPNs, NAT, DNS, DHCP, routing, certificates, and diagnostics through natural language, with guardrails, rate limits, and config-revision backups that make destructive changes reversible.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants and MCP clients to execute commands, copy/move files, manage background jobs and port forwarding, and optionally view and control remote screens using scoped, expiring agent tokens.
      8 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have distinct resource/action targets, and descriptions clearly separate policies, endpoints, alerts, events, and intel feeds. Minor overlap exists between global intel sources, customer intel feeds, and policy intel source management, but the descriptions provide enough context to choose correctly.

    Naming Consistency4/5

    The set mostly follows a predictable snake_case verb_noun convention such as list_policies, show_endpoint, create_policy, and upgrade_endpoints. Exceptions like whoami, agent_install_instructions, and the multi-action manage_* tools are minor deviations but still readable.

    Tool Count3/5

    The 25 tools cover several broad domains—policies, endpoints, intel feeds, alerts/events, and agent onboarding—so most tools are justified. However, the surface is heavy and at the upper boundary where discoverability and selection cost become significant.

    Completeness3/5

    Core workflows are covered: policy creation/cloning/enforcement, rule and intel attachment, endpoint listing/upgrades, alert triage, and enrollment. Notable lifecycle gaps remain, including policy update/delete/disable or default assignment, rule removal, and endpoint unenrollment/deletion.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing