Skip to main content
Glama
bonklek

p2p-tools-mcp

by bonklek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to p2p-tools-mcp

No user-submitted related servers found.

    Related Servers

    • rtorrent-mcp

      sandraschi
      A
      license
      B
      quality
      A
      maintenance
      MCP server for rTorrent BitTorrent automation, enabling torrent management (add/list/pause/delete), multi-source searching (Nyaa, Pirate Bay, etc.), and post-processing workflows via natural language.
      7
      1
      MIT

    • qui-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server that exposes qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.
      12
      MIT

    • MPilot

      davezfr
      A
      license
      Not graded
      quality
      B
      maintenance
      Unified MCP server for media acquisition, subtitle automation, and agent-run media workflows, enabling downloads via Prowlarr/qBittorrent and subtitle translation/sidecar creation.
      1
      MIT

    • arr-mcp

      bardesss
      A
      license
      Not graded
      quality
      A
      maintenance
      A unified MCP server for your self-hosted media stack (Radarr, Sonarr, Jellyfin, etc.). It correlates across services to answer questions no single service can, with safety features like untrusted-output fencing and safe-by-default deletions.
      56
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connect, disconnect, check status, get public IP, and enforce an active connection. No two tools overlap in functionality, reducing the chance of misselection.

    Naming Consistency4/5

    All tools share the vpn_ prefix and use snake_case, which is consistent. There is a slight mix of verb-based names (vpn_connect, vpn_disconnect, vpn_require_active) and noun-based names (vpn_status, vpn_public_ip), but the pattern remains predictable and readable.

    Tool Count5/5

    Five tools is a well-scoped set for a VPN control server, covering the essential operations without unnecessary redundancy. The count is appropriate for the domain and neither sparse nor bloated.

    Completeness4/5

    The tool set covers the core VPN lifecycle: connect, disconnect, status, public IP, and an active-connection guard. Minor gaps exist, such as listing available countries or retrieving current server details, but these are not critical for basic workflows and can be worked around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources