Some Meraki switches, including MS250 have a physical Management Interface, but as @alessandrodematos says, it's not anything like a Catalyst console port. It (and in fact any other LAN port) instead provides local wired access to the Local Status Page - a small web GUI. The LSPs main role is just to provide a way for an admin to apply sufficient initial config to get the switch talking to the Meraki Dashboard, where all the real magic happens!
Bearing in mind that, out of the box, the switch will work much like a PC in learning IP config via DHCP, most customers don't need to use the LSP; they just ensure its uplink towards the Internet allows DHCP and allows it to contact the relevant resources in the meraki cloud.
https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MS_Series
Also worth knowing about the Meraki Dashboard API - consider this to be a multi-headed console cable, with one end plugged into the Internet (but only accessible by admins with the right API key), with the other ends always plugged into the back of every Meraki switch (and AP and MX and MV camera etc. etc.) in your Dashboard. The API provides freedom to issue 'console commands' to numerous devices, programatically! https://developer.cisco.com/meraki/api-v1/
