Manage game servers, Discord bots, apps and VPS: power, console, files, backups and deploys.
MCPpedia last refreshed this data
io.github.CloudCorpRecords/hostdeck is an MCP server that manage game servers, Discord bots, apps and VPS: power, console, files, backups and deploys. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"hostdeck": {
"args": [
"-y",
"@reneturcios/hostdeck",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Manage game servers, Discord bots, apps and VPS: power, console, files, backups and deploys.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/hostdeck' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/hostdeck against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in productivity / entertainment
The official MCP Server for the Mux API
Official MCP server for Anytype API - your encrypted, local and collaborative wiki.
Give Claude the ability to watch and understand videos — Claude Code plugin with frame extraction and multimodal audio analysis
MCP server for monday.com integration.
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/hostdeck and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
hostdeck is a small local bridge to FadeHost's hosted MCP server, which looks after an account's game servers, Discord bots, hosted apps and VPS instances. From one surface you can power machines on and off, read consoles, edit server files, take backups, deploy apps from a repository, and keep an eye on usage and firewalls.
The bridge keeps no hosting data and runs no hosting logic of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched.
Game servers:
list_servers — every game server the account can
manage (own plus team-shared), with id, game, status
and address. Call this first to discover server ids.
No arguments.get_server — one server in full: status, software
and version, RAM/disk usage, key settings, ports, node
type and the most recent crash diagnosis. Required:
server.get_console_logs — recent raw console output.
Required: server. Optional: lines (50-400,
default 150).get_live_stats — live memory and CPU usage of a
running server. Required: server.get_player_activity — join/leave/chat counts and
recent players over a window. Required: server.
Optional: hours (1-168, default 24).start_server, stop_server, restart_server —
power actions through the same guarded paths as the
panel buttons; stop and restart save the world first.
Required: server.send_console_command — run one console command on a
running Minecraft server over RCON, without a leading
slash. Required: server, command.Backups and worlds:
list_backups — off-site backup snapshots of a
server (id, time, size). Required: server.create_backup — trigger an off-site backup now.
Required: server.get_world_activity — chunk counts, disk use and
pruning headroom for a Minecraft Java world.
Required: server.prune_world — remove barely-visited chunks; dry
run by default. Required: server. Optional:
threshold, dry_run.undo_world_prune — restore the world files from
before the most recent prune. Required: server.Creation:
create_server — create a game server, optionally
from a preset or with per-game options. Required:
name. Optional: game, software, version,
region, ram_mb, preset, options.get_creation_options — the presets and per-game
options create_server accepts. Optional: game.create_app — deploy a Discord bot or web app from
a GitHub or GitLab repository. Required: name,
repo_url. Optional: kind, region, tier,
runtime, branch, start_command, build_command,
build_mode, env, web_address, port.Files:
list_files — list a directory in a server's file
system (jailed to that server). Required: server.
Optional: path.read_file — read a text file (capped at 96KB;
binary files are refused). Required: server,
path.write_file — create or overwrite a text file
(capped at 192KB; overwrites without backup).
Required: server, path, content.Bots and apps:
list_bots — the hosted Discord bots on the account:
id, name, status, runtime and source repo. No
arguments.get_bot_logs — runtime logs of a hosted bot.
Required: bot.power_bot — start, stop or restart a hosted bot.
Required: bot, action (start, stop or
restart).redeploy_app — pull the latest commit of a hosted
app or bot and start it again. Required: app.list_app_deployments — deploy history: commits,
newest first, and which commit is live. Required:
app.rollback_app — pin an app to an earlier commit, or
follow the latest again. Required: app. Optional:
commit.get_app_usage — plan limits, latest and peak
readings, and traffic for an app. Required: app.get_app_firewall — the outbound policy and rules
an app runs under. Required: app.