BunkerWeb MCP
OfficialRelated Servers
Alternatives to BunkerWeb MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that wraps CubeCoders AMP to list, inspect, and control game-server instances.85MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Mobilerun platform, exposing tools for device control, workflow automation, task management, and platform operations via a stateless HTTP or stdio interface with bearer-token authentication and policy-based access control.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server providing file, system, math, and text utilities through a simple CLI client.-
- AlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) and exposes their combined tools and resources through a single unified SSE or Streamable HTTP endpoint, or as a standalone Stdio server. It routes requests to the correct backend, supports optional API key/bearer token authentication, and offers an optional web admin UI for managing servers, toggling tools, and monitoring installations.120 npmMIT
- AlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) into a single hub, exposing their combined tools and resources through unified SSE or Streamable HTTP endpoints, or as a Stdio server, while routing requests to the correct backend. Adds API-key/bearer-token endpoint security, per-tool enable/disable and renaming, and an optional web admin UI with live config reload, install monitoring, and a web terminal.120 npmMIT
- FlicenseNot gradedqualityAmaintenanceA meta-MCP server that aggregates and proxies other MCP servers, letting LLMs search for, add, configure, enable, disable, and bundle backend servers at runtime. Tools from those servers are automatically exposed under unified prefixes, with persistent configuration, health checks, and support for stdio, HTTP, and hybrid transports.-
TDQS
Scored across 37 tools
Despite 37 tools, each targets a distinct resource+action and descriptions explicitly cross-reference siblings (ping_api vs diagnose_bunkerweb vs ping_instances; list_instances vs get_instance; stop_instances vs reload_instances; text vs file variants of config tools). Boundary cases like create_config vs create_configs_from_files or list_bans vs list_cache_files are spelled out in-line, so an agent can reliably choose.
Consistent verb_noun pattern throughout (list_/get_/create_/update_/delete_/ping_/run_ + resource), with singular vs plural used meaningfully to signal single-item vs batch operations (get_instance vs delete_instances, ban_ips vs list_bans). No camelCase or style mixing.
The 37 tools span roughly eight real sub-domains (instances, services, global config, config snippets, plugins, jobs, cache files, bans) so most earn their place, but the total is heavy and some pairs (create_config/create_configs_from_files, update_config/update_config_from_file, ping_api/diagnose_bunkerweb) could be consolidated via parameters.
Coverage is strong: full CRUD on instances, services, global config and snippets, plus plugin install/uninstall, ban/unban, cache read/delete, job triggering, diagnostics and docs search. Minor gaps remain around API token lifecycle (create only, no list/revoke) and instance start (stop exists but restart is explicitly out of scope).