If the command needs to go via TCP, I don't believe you can send it as a network cue.
When I've had to use TCP commands (with a Blackmagic Hyperlink deck, which has a robust TCP protocol), I've used script cues that send "do shell script" TCP commands via netcat ("nc" for short, a fact that makes it notoriously difficult to locate in search engines). This was enough of a pain to resolve that I wrote a pretty long "note to self" on the Blackmagic forum that walks through how to send "one-off" TCP commands via shell script. If it's truly just a "connect to Neets via TCP, send a command, and close down the TCP connection" you're looking to do, this will do the trick.
I hope this is helpful! For as fundamental a concept as TCP is, I was amazed how hard it was to find basic info about how to use it.
Cheers,
Matt