I've been a Meraki MX user since Nov '14 and I think it's a great product but it lacked a community for it's users to collaborate on the direction we want the product to go in with new features. I want this to get the attention of Meraki and hopefully they'll join us in implementing these features.
1/4/16 Update: Meraki has begun responding to various posts!
Right now this site running on the free version of UserEcho so it doesn't have some features I'd like it to have (such as tagging).
Rob Geoghan
rgeoghan {at} gmail.com

Show LAN port statistics on MX
You should be able to see how much data and other stats on a LAN port by LAN port basis on the MX line.

Show resource usage on the MX devices

Limit VPN users to a specific group in Active Directory

Alert when WAN 2 goes down
You can't set alerts on the secondary WAN connection. It would really suck to be paying for a secondary WAN connection only to not notice that it went down for a long time without you noticing it.

Basic print server function

Show firmware version in dashboard
I recently was troubleshooting an issue that I was experiencing on one of my two MX64s devices. The only difference I believed what that they were running different firmware versions but I needed to cal into support to find that out. They changed the firmware to match the version of the other MX64 and my problem went away.

Enable wake on LAN (WOL) on MX series

Persistent Local Log storage
Devices need to be re-designed to have a way to store Local logs in persistent storage somehow.
Reasoning:
When there is a bad software release or hardware issue, we are always asked to retrieve the local status logs. In high uptime environments, that turns a 5 minute outage, into a 30 minute outage sometimes. We understand that this is required for Cisco to troubleshoot. However, Cisco does not suffer the financial cost of this downtime, nor do they reimburse us for this in anyway.
If the local status logs are required for troubleshooting by Cisco, then Cisco needs to implement ways to guarantee those logs are stored in a way they can be retrieved, especially if your primary 1st step for all troubleshooting is "just restart it", thus dumping all the logs you would need to actually diagnose the issue.
It almost doesnt even make sense that Meraki as a product line went into the market without this functionality.
Customer support service by UserEcho