Skip to main content
Glama
Alex0neS

remnawave-mcp

by Alex0neS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to remnawave-mcp

No user-submitted related servers found.

    Related Servers

    • Remnawave MCP Server

      grader-devops
      A
      license
      Not graded
      quality
      C
      maintenance
      Wraps the Remnawave panel API into 22 callable tools so AI assistants can manage VPN nodes, users, squads, config profiles, and hosts through natural language instead of manual curl requests. It supports listing, creating, enabling, disabling, restarting, and extending entities, along with traffic resets and node key generation, using credentials supplied via environment variables.
      2
      Apache 2.0

    • mcp-remnawave

      Maaagiic
      A
      license
      C
      quality
      A
      maintenance
      Enables MCP clients like Claude Code, Claude Desktop, or Cursor to read and manage Remnawave 3.x VPN panel resources — users, nodes, hosts, config profiles, squads, subscription templates, billing, and HWID devices — through the panel's REST API, with contract-driven tool schemas, numeric user IDs, multi-panel config lookup, and an optional readonly mode.
      204
      5 npm
      MIT

    • remnawave-mcp

      folexz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to manage a Remnawave panel through its full API, covering users, nodes, hosts, subscriptions, and more with configurable tool profiles and read/write token access.
      4 npm
      MIT

    • aapanel-mcp

      devochkaskustikom
      A
      license
      B
      quality
      B
      maintenance
      Enables AI CLI agents to operate an aaPanel (btPanel fork) hosting panel through its signature-authenticated HTTP API, exposing 57 described operations covering websites, databases, SSL certificates, backups, and system status plus resources for panel inventories. Ships with a read-only default mode and a separate gate over credential-exposing and file-level operations, redacting generated passwords from tool results.
      59
      10 npm
      MIT

    • remnawave-mcp

      3APA3A-3AHO3A
      A
      license
      C
      quality
      A
      maintenance
      Enables Claude Desktop, Cursor, and other MCP clients to inspect a Remnawave 3.x panel through natural-language chat, covering users, nodes, traffic, devices, connections, and GeoCheck, with tools generated from the official backend contract to match the panel version. Read-only by default and privacy-filtered, so secrets, keys, and client identifiers are hidden or replaced with aliases before reaching the chat.
      85
      5 npm
      2
      MIT

    • iPaaS MCP Server

      providcc
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 20 read/write tools that let IDE and agent users search the interface catalog, build and validate flow-model JSON, import OpenAPI specs, run ETL tasks, and plan or revoke service permissions on RestCloud-compatible integration platforms. Writes default to dry-run and every call is written to a desensitized jsonl audit trail.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.3/5.0

    Scored across 222 tools

    Disambiguation2/5

    With 222 tools, many endpoints overlap in purpose (e.g., two internal squad usage tools, offset vs cursor user listing, multiple subscription getters), forcing the agent to read fine-grained descriptions to choose correctly. The controller prefixes help somewhat, but the volume and near-duplicate names make misselection likely.

    Naming Consistency3/5

    Names generally follow a resource_action snake_case pattern (users_create_user, nodes_restart_node), but inconsistencies appear: random suffixes like _1r7914, a typo (infra_billing_delte_infra_provider), and mixed get vs get_all conventions. Still, the dominant pattern is readable.

    Tool Count1/5

    222 tools vastly exceeds a reasonable MCP surface (calibration marks 50+ as extreme mismatch), overwhelming the agent and making navigation costly despite helper tools like api_search.

    Completeness5/5

    The surface covers nearly all Remnawave panel domains (users, nodes, hosts, squads, configs, billing, subscriptions, auth, passkeys, metrics, etc.) with full CRUD and bulk operations, leaving few obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources