Player-session MUD protocol

MCCP3

MUD Client Compression Protocol v3

Niche use Documented current use

Adds client-to-server compression as the reverse-direction complement to MCCP2.

Protocol overview

First seen: 2019
Present-day status: Niche use
In use today?: Yes, with documented current use.
Legacy?: No.
Layer: Player-session MUD protocol
Transport: Telnet option 87 with client-to-server zlib
Telnet option: 87
Research validated: 2026-08-29

Current use and fit

Implemented by TinTin++ and some reference handlers, but adoption and practical bandwidth benefit are limited.

Implementation essentials

Negotiate inbound compression independently from MCCP2.
Decompress before feeding bytes to the Telnet parser.

Compatibility and safety notes

Client command traffic is normally small.
Compression is not security and does not protect passwords.

Original specifications and sources

MUDhalla MCCP specification Primary
MUD Standards preservation Preservation

Where an original site has disappeared, a preservation archive is linked and identified as such. MUDVerse does not claim authorship of the original protocol.