An IRC protocol frontend for an NMDC server.

This program 'wraps' an NMDC server to make it available to IRC clients. It implements the IRC server protocol, but is not itself an IRC server, deferring to the upstream NMDC server in all salient cases. From a layering perspective it occupies the same position as the web interface.

The intent of this project is to expand client library and application support on platforms where the NMDC community has not been able to spend effort (e.g. Apple iOS client, ruby/rust/erlang libraries, greater choice in web interfaces).

TLS (SSL) support is not integrated. To host the IRC frontend over TLS, please use a reverse proxy in much the same manner as for NMDCS.


This program uses some code from the AGPLv3 project , from which it inherits the Affero GPLv3 license. Anyone hosting a modified version of this software is required to release their changes under the terms of the AGPLv3.


  • Seamless roundtrip transition between NMDC /me and IRC CTCP ACTION
  • IRC client's "Real Name" exposed as NMDC Description
  • IRC client's CTCP VERSION exposed as NMDC client tag, with heuristic truncation
  • NMDC server's title exposed as IRC channel topic
  • Login with passworded nick (classic PASS, not SASL)
  • Full nick list integration including op status
  • Support IRC client changing nick via NMDC upstream reconnection
  • Automatic join to single-enforced chatroom
  • Multithreaded
  • Single binary deployment


Usage of nmdc-ircfrontend:
        Automatically join clients to the channel (default true)
  -bind string
        The address:port to bind to and listen for clients on (default ":6667")
  -hubsecurity string
        Nick used for administrative events (default "Hub-Security")
  -servername string
        Server name displayed to clients (default "nmdc-ircfrontend")
  -upstream string
        Upstream NMDC/ADC server (default "")
        Display debugging information


This section was last updated on or around the release of 1.3.0. Current compatibility may differ.

NMDC's smaller community has standardised around comparatively few protocol implementations by means of necessity. In comparison, there are a lot of IRC client implementations with slightly differing interpretations of the protocol.

For passworded DC usernames, your IRC PASS username must be the same as your IRC nickname.

Tested working:

  • AndChat
  • AndroIRC
  • Atomic
  • Hexchat
  • HoloIRC
  • Irssi
  • LiteIRC
  • Mango IRC
  • mIRC 7
  • Mutter
  • Revolution IRC
  • Weechat
  • Yaaic


  • 0.6x IRC plugin (can join room and recieve PMs after some regex tweaking)


2018-03-24 1.3.0

2017-05-28 1.2.3

2017-05-27 1.2.2

2016-11-29 1.2.1

2016-08-27 1.2.0

2016-05-10 1.1.0

2016-05-08 1.0.0