# Node Client

**URL:** <https://mediasoup.discourse.group/t/node-client/6811>\
**Category:** mediasoup libraries\
**Created:** [August 7, 2025, 5:56pm UTC](https://mediasoup.discourse.group/t/node-client/6811 "2025-08-07T17:56:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ericwood73](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ericwood73/32/2915_2.png) [@ericwood73](https://mediasoup.discourse.group/u/ericwood73)\
**Post date:** [August 7, 2025, 5:56pm UTC](https://mediasoup.discourse.group/t/node-client/6811/1 "2025-08-07T17:56:24Z")

</div>

Are there any actively maintained node.js client libraries for mediasoup? We were using [msc-node](https://github.com/shinyoshiaki/mediasoup-client-node), but it doesn’t work with mediasoup 3.6 and above and doesn’t appear to be actively maintained. We need a node client for bots we use in our application that proxy for users for testing at scale.

---

<div class="post-metadata">

**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\
**Post date:** [August 10, 2025, 12:40am UTC](https://mediasoup.discourse.group/t/node-client/6811/2 "2025-08-10T00:40:38Z")

</div>

Are you seriously asking if there’s an actively maintained Node.js client for mediasoup? The official mediasoup client exists, works with 3.6+, and is actively maintained. Using msc-node for bots at scale sounds like a recipe for failure—if you want reliable testing at scale, switch to the official client and stop wasting time on abandoned projects.

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [August 10, 2025, 6:07am UTC](https://mediasoup.discourse.group/t/node-client/6811/3 "2025-08-10T06:07:40Z")

</div>

What’s he means is that that fork of mediasoup-client supports [werift-webrtc](https://github.com/shinyoshiaki/werift-webrtc) which is supposed to be a complete WebRTC stack for Node (ICE, DTLS, SRTP, etc).

But rather than looking for a complete fork of mediasoup-client, what he should do is copy&paste the src/handlers/werift.ts handler in the [fork](https://github.com/shinyoshiaki/mediasoup-client-node), adapt it to make it compatible with latest HandlerInterface class of mediasoup-client and then read the docs of the mediasoup-client Device class constructor or factory() static method which allow passing a handlerFactory argument.
