ark-asa-mcp
The ark-asa-mcp server provides an MCP interface to manage Ark: Survival Ascended game servers via RCON, enabling configuration management, remote administration, and game interaction.
Server Configuration Management
List all configured RCON servers (passwords excluded)
Add or update named server entries in
config.json(host, port, password, timeout, response cap)Remove a named server entry from
config.jsonSet a default server used when
serverNameis not specified
RCON & Game Administration
Run any single-line raw RCON command (newlines rejected to prevent command batching)
List currently connected players, returning raw output and parsed player entries
Broadcast custom messages (up to 512 characters) to all connected players
Trigger a world save to persist current game state
Retrieve recent game log output from the server
Multi-Server Support
All RCON tools accept an optional
serverNameargument to target a specific server when multiple are configured
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ark-asa-mcp who is online on my ark server?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ark-asa-mcp
ark-asa-mcp is a Node.js Model Context Protocol server for Ark: Survival Ascended servers that expose RCON.
It lets an MCP client run common ASA administration commands through a small, typed tool surface while keeping one or more RCON server definitions in a local config.json file.
Features
MCP stdio server built with
@modelcontextprotocol/sdk.RCON command execution against one or more named Ark: Survival Ascended servers.
Per-tool
serverNamerouting when multiple servers are configured.Convenience tools for listing players, broadcasting messages, saving the world, and reading the game log.
Centralized configuration through
config.json.Unit-tested command helpers for input validation and output shaping.
Related MCP server: ark-wiki-mcp
Requirements
Node.js 20 or newer.
One or more Ark: Survival Ascended servers with RCON enabled.
The RCON host, port, and password for each configured server.
Install
Developer mode:
npm install
npm run buildUser mode:
Download ark-asa-mcp-win-x64.zip from a GitHub release, extract it, copy config.example.json to config.json, and point your MCP client at ark-asa-mcp.exe.
Configuration
Copy config.example.json to config.json and edit the server definitions for your ASA hosts. The local config.json file is ignored by Git because it contains RCON passwords.
{
"defaultServerName": "azer",
"timeoutMs": 10000,
"maxResponseChars": 20000,
"servers": [
{
"serverName": "azer",
"host": "127.0.0.1",
"port": 27020,
"password": "change-me"
},
{
"serverName": "island",
"host": "127.0.0.2",
"port": 27020,
"password": "change-me-too"
}
]
}By default, ark-asa-mcp reads config.json from the process working directory. You can point to another file with ARK_ASA_CONFIG_PATH:
ARK_ASA_CONFIG_PATH=D:/Repositories/ark-asa-mcp/config.jsonEach server object supports:
Field | Required | Default | Notes |
| yes | none | Stable name used by MCP tools, such as |
| no |
| ASA RCON host. |
| no |
| ASA RCON port. |
| yes | none | ASA RCON password. |
| no | top-level | Per-server timeout override. |
| no | top-level | Per-server response cap. |
defaultServerName is optional. If it is not set and only one server is configured, tools can omit serverName. If more than one server is configured, tools should pass serverName.
Environment fallback is still available for simple or containerized deployments:
ARK_ASA_RCON_SERVER_NAME=azer
ARK_ASA_RCON_HOST=127.0.0.1
ARK_ASA_RCON_PORT=27020
ARK_ASA_RCON_PASSWORD=change-meARK_ASA_RCON_SERVERS and ARK_RCON_* aliases are still accepted as fallbacks when no config file exists.
MCP Client Example
Release .exe mode:
{
"mcpServers": {
"ark-asa": {
"command": "C:/Tools/ark-asa-mcp/ark-asa-mcp.exe"
}
}
}If the config file lives elsewhere:
{
"mcpServers": {
"ark-asa": {
"command": "C:/Tools/ark-asa-mcp/ark-asa-mcp.exe",
"env": {
"ARK_ASA_CONFIG_PATH": "C:/Tools/ark-asa-mcp/config.json"
}
}
}
}Node mode:
{
"mcpServers": {
"ark-asa": {
"command": "node",
"args": ["D:/Repositories/ark-asa-mcp/dist/index.js"],
"env": {
"ARK_ASA_CONFIG_PATH": "D:/Repositories/ark-asa-mcp/config.json"
}
}
}
}For development, you can point the command at tsx:
{
"mcpServers": {
"ark-asa-dev": {
"command": "npx",
"args": ["tsx", "D:/Repositories/ark-asa-mcp/src/index.ts"],
"env": {
"ARK_ASA_CONFIG_PATH": "D:/Repositories/ark-asa-mcp/config.json"
}
}
}
}Tools
Tool | Purpose |
| Lists configured ASA RCON servers without exposing passwords. |
| Lists servers from |
| Creates or updates a server entry in |
| Removes a server entry from |
| Sets the default server in |
| Runs a raw RCON command. |
| Runs |
| Runs |
| Runs |
| Runs |
Server-bound tools accept an optional serverName argument. It becomes required when multiple servers are configured and no default server is set.
Config-writing tools never return passwords, but any password supplied through an MCP client is still visible to that client. For local setup, ark-asa-mcp configure is safer.
The MCP server can start before any server is configured so asa_config_upsert_server can create the first config.json. RCON tools will return a clear error until at least one server exists.
CLI Commands
ark-asa-mcp configure
ark-asa-mcp configure --server-name azer --host 127.0.0.1 --port 27020 --password change-me --default
ark-asa-mcp config:list
ark-asa-mcp --versionconfigure creates or updates config.json interactively.
Releases
The release workflow builds a Windows x64 zip containing:
ark-asa-mcp.execonfig.example.jsonREADME-USER.mdLICENSE
Push a tag like v0.1.0 to create or update a draft GitHub release asset.
Development
npm run typecheck
npm test
npm run buildThe package entry point is src/index.ts. Build output is written to dist/.
Windows executable packaging uses Node.js single executable applications:
npm run package:winThis script expects Node.js 26 or newer.
Security Notes
RCON has server administrator authority. Treat every RCON password like a production secret, avoid committing .env files, and only expose this MCP server to clients you trust.
The raw command tool intentionally supports arbitrary single-line RCON commands. Newline characters are rejected to prevent accidental command batching.
Available Tools
10 toolsasa_broadcastBroadcast ASA MessageB
Broadcast a message to connected Ark: Survival Ascended players.
Inputs: message (required), serverName.
asa_config_list_serversList ASA Config ServersB
List servers from config.json without exposing passwords.
Inputs: no named parameters.
asa_config_remove_serverRemove ASA Config ServerB
Remove a named ASA RCON server from config.json.
Inputs: serverName (required).
asa_config_set_default_serverSet Default ASA Config ServerB
Set the default ASA RCON serverName in config.json.
Inputs: serverName (required).
asa_config_upsert_serverAdd or Update ASA Config ServerB
Create or update a named ASA RCON server in config.json.
Inputs: serverName (required), host, port, password, +3 more.
asa_get_game_logGet ASA Game LogC
Run GetGameLog on the Ark: Survival Ascended server.
Inputs: serverName.
asa_list_playersList ASA PlayersB
Run ListPlayers and return raw output plus parsed player entries.
Inputs: serverName.
asa_list_serversList ASA RCON ServersA
List configured Ark: Survival Ascended RCON servers without exposing passwords.
Inputs: no named parameters.
asa_rcon_commandRun ASA RCON CommandC
Run one raw Ark: Survival Ascended RCON command.
Inputs: command (required), serverName.
asa_save_worldSave ASA WorldB
Run SaveWorld on the Ark: Survival Ascended server.
Inputs: serverName.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools target distinct actions, but asa_list_servers and asa_config_list_servers appear to do nearly the same thing, creating real selection risk. The specialized RCON wrappers are clearly described, though asa_rcon_command can overlap with them by design.
All names use the asa_ prefix and snake_case, and most follow a verb_noun pattern such as asa_list_players and asa_save_world. The config tools consistently use asa_config_<verb>_<object>, with minor deviations like asa_rcon_command and asa_broadcast.
10 tools is well-scoped for a server that manages ASA RCON server configuration and provides common RCON operations. Each tool has a plausible role in the workflow, and the count is solidly within the ideal range.
The config lifecycle is covered with list, upsert, remove, and set-default, while RCON coverage includes a raw command plus wrappers for players, broadcast, save world, and game log. A direct status or connection-check tool is missing, but the raw RCON command provides a fallback for many edge cases.
Maintenance
Related MCP Connectors
Manage game servers, configurations, players, and groups through the GameServerApp MCP server.
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server for AI dialogue using various LLM models via AceDataCloud
An MCP server for deep research or task groups
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server for managing and operating Minecraft servers through multiple backend protocols including MCSManager API, RCON, and MSMP. It provides tools for instance lifecycle management, file operations, console commands, player administration, and server configuration with built-in security controls.712MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets Claude answer ARK: Survival Ascended / Evolved questions by querying the ARK community wiki for taming, crafting, spawns, and stats.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets Claude check your Nitrado-hosted ARK server: live status, settings, and files without using the web panel.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for managing Exaroton game servers via natural language, enabling server lifecycle control, file management, player lists, and configuration editing.-