ark-nitrado-mcp

An MCP server that lets Claude check your own Nitrado-hosted ARK: Survival Ascended / Evolved server: live status, configured settings, and server files — without you having to dig through the Nitrado web panel yourself.

This is a companion to ark-wiki-mcp (general ARK game knowledge). This one is specific to your server and requires your own Nitrado credentials — nothing server-specific is bundled in this repo.

Tools

• list_services() — list all services on your Nitrado account with their service_id, to find which one is your ARK server.

• get_server_status(service_id?) — online/offline, IP/port, slots, game version.

• get_server_settings(service_id?, reveal_passwords?) — server rates, difficulty, PvE/PvP, mods, and other config, as reported by Nitrado's API. Passwords are masked by default.

• list_server_files(path, service_id?) — browse files on the server's storage.

• read_server_file(path, service_id?) — read a specific file's raw contents, e.g. arksa/ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini.

service_id is optional on every tool if you configure a default one at install time.

Related MCP server: ark-asa-mcp

Setup

1. Get a Nitrado API token: log into nitrado.net → account menu → Developer Portal → Long-life tokens → enable the service permission → generate a token.

   Changing your Nitrado account password revokes all existing tokens.

2. Install the plugin:

   /plugin marketplace add chelseyklein/ark-nitrado-mcp
   /plugin install ark-nitrado-mcp@ark-nitrado-mcp

   You'll be prompted for the token (stored in your system keychain, never written to disk in plain text or committed anywhere) and, optionally, your server's service_id. If you don't know your service_id yet, leave it blank and ask Claude to run list_services() once the plugin is installed.

Requires Python 3.10+ available as python on your PATH. Dependencies (requests, mcp) install automatically on first run.

Security notes

• Your token and service ID live only in your local Claude Code config/keychain — never in this repo.

• get_server_settings masks password-like fields by default; pass reveal_passwords=true explicitly if you need to see them.

• The account behind the token should be treated like any other credential: don't paste it into chat, tickets, or logs.

How it works

Talks directly to Nitrado's REST API (api.nitrado.net) using a bearer token — no FTP/SFTP required, since Nitrado exposes a file-manager endpoint over the same API for reading server files.

License

MIT