Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Hostdeck

by CloudCorpRecordsversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.CloudCorpRecords/hostdeck

Install

Overview

Description from the maker (original English)

Manage game servers, Discord bots, apps and VPS: power, console, files, backups and deploys.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "hostdeck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hostdeck",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add hostdeck -- npx -y @reneturcios/hostdeck mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "hostdeck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hostdeck",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "hostdeck": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/hostdeck",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

  • More stars than 0% of the other 1760 servers in this category
  • Published to the registry more recently than 91% of the other 1760 servers in this category
  • Basic checks equal to or better than 100% of the other 1760 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Hostdeck safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago
Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 30 days ago
Install

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

hostdeck

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.

Tools

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.
  • set_app_firewall — replace the outbound list of a paid app: open, or allowlist with rules. Required: app, policy. Optional: rules.
  • get_app_refusals — what the firewall actually turned away in the last day. Required: app.
  • list_app_schedules — scheduled commands of an app, with ids, last runs and next runs. Required: app.
  • create_app_schedule — add a cron-scheduled shell command to an app. Required: app, cron, command. Optional: enabled.
  • delete_app_schedule — remove a scheduled command. Required: app, schedule_id.
  • move_app_region — move a paid app to another region, or read where it runs now. Required: app. Optional: region.
  • list_app_variables — the NAMES of an app's environment variables (values are never returned). Required: app.
  • set_app_variables — add, change or remove environment variables. Required: app. Optional: set, unset.

VPS instances:

  • list_vps — the account's managed VPS instances with id, plan, specs, status, region and SSH host. No arguments.
  • power_vps — start, shut down or reboot a VPS. Required: vps, action (start, shutdown or reboot).

Configuration

  • FADEHOST_MCP_URL (optional) — override the upstream endpoint. Defaults to https://api.fadehost.com/mcp. (The override hook is this rebuild's own labelled reconstruction.)
  • FADEHOST_API_KEY (optional) — when set, every upstream request carries an X-API-Key: header; the header name is the one the upstream's registry record declares. When it is not set, no such header is sent. (The env name and this forwarding are also a labelled reconstruction; the original surface was captured keyless.)
Forwarding mechanics

On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name hostdeck), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with hostdeck error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):

npx @reneturcios/hostdeck list_servers

npx @reneturcios/hostdeck get_server '{"server":"server_42"}' npx @reneturcios/hostdeck send_console_command '{"server":"server_42","command":"list"}' npx @reneturcios/hostdeck --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/hostdeck mcp

MCP client config:

{

"mcpServers": { "hostdeck": { "command": "npx", "args": ["-y", "@reneturcios/hostdeck", "mcp"] } } }

Docker

docker run -i ghcr.io/cloudcorprecords/hostdeck

docker run --rm ghcr.io/cloudcorprecords/hostdeck --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

npm install

npm run build npm test npm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.

Ask PopNx