MBeans are not a "design pattern". An MBean is an interface standard that is part of JMX. It means nothing outside of JMX. There would be no direct equivalent in other languages unless JMX defined API bindings in other languages, which it doesn't.
The reason they exist is because it was prudent for JMX to define a common interface standard for dealing with these objects.
The problem they intend to solve is to give a consistent standardized interface that JMX can work with.
There may be APIs with bindings in other languages that have similar functionality to JMX, but they would not use MBeans, they would use whatever is defined in those other APIs.
If you are not using JMX then it would make no sense to use an MBean. In fact, if you are not using JMX, you could argue that even if you called something an "MBean", it conceptually would not be one.