NHN

You run an MCP server that lets you securely execute commands on remote hosts through an SSH gateway, with Kerberos authentication, command whitelisting, and dynamic configuration reloads. It centralizes control, enforces safety rules, and provides server information to an automation layer.

How to use

To operate the NHN MCP server, you connect through your MCP client and issue allowed commands to target hosts via the SSH gateway. The server enforces a whitelist of permitted commands, blocks risky patterns, and can fetch or display server information to help you verify logs and paths. You can remotely trigger command execution, reload configuration on the fly, and monitor connection status. Use this flow: configure your client to point at the MCP endpoint, ensure Kerberos credentials are available, and run commands from the allowed set against the permitted hosts.

How to install

Prerequisites: you need Node.js installed on the machine where you set up the MCP server.

npm install
npm run build

Configuration and usage notes

Create a configuration file named config.json with gateway connection details, authentication, allowed targets, and safety rules. The following example shows the structure you will implement.

{
  "gatewayConnection": "user@gateway.example.com:22",
  "gatewayPassword": "your-password",
  "kinitPassword": "your-kerberos-password",
  "allowedHosts": ["server1", "server2"],
  "blockedPatterns": [">", "`", "$(", ";", "&&", "||"],
  "allowedCommands": [
    "tail", "head", "cat", "grep", "ls", "ps", "whoami"
  ],
  "serverInfo": {
    "서버에 대한 user 정보 필수": "exec 할때 user 를 같이 보냅니다.",
    "나머지는": "원하는 내용으로",
    "ex - logPaths": {
      "app": "/var/log/app.log",
      "nginx": "/var/log/nginx/access.log"
    }
  }
}

Running the MCP server

After you have built the project, start the MCP server using a Node runtime pointing to the built entry point. You also need to provide the path to your config.json via an environment variable or configuration loading mechanism.

node /path/to/nhn-server-mcp/dist/index.js

Available tools

exec

Execute a command on a target server through the MCP server with safety checks and a specified host and user.

get_config

Query current MCP server configuration including allowed hosts, commands, and server info to verify runtime behavior.

reload_config

Reload the configuration file without restarting the MCP server to apply changes on the fly.

disconnect_server

Terminate the gateway connection to the remote server from the MCP session.

connection_status

Check the current status of active MCP connections and sessions.