title: Issue with "Meteor mongo" command when connected to separate Mongo Instance
body: <p>When running the "parties" example locally, if I first specify my MONGO_URL to use an already existing mongo instance <code>meteor mongo</code> reports that meteor isn't running, even though it is and even though it is connecting just fine to a separate mongo instance.</p>
  
  <p>If you run the meteor app without specifying a separate MONGO_URL, no problems <code>meteor mongo</code> works as expected</p>
  
  <p>Now I have also tried setting the MONGO_URL before running <code>meteor mongo</code> to no avail. I haven't tried deploying the app to see what would happen. </p>
  
  <p>The one other attempt to troubleshoot is after running the app, I try to connect using meteor mongo with the  <code>--url localhost:27017</code> flag it asks for a <strong>Password:</strong>. This is supposed to give me a URL to connect to the database instance, and the request for a Password isn't mongo either, since </p>
  
  <p>a) I don't have authentication enabled on my local instance</p>
  
  <p>b) Even if the local instance isn't running and you run <code>meteor mongo</code> it still asks for a password.</p>
  
  <p>In the meteor documentation it notes under meteor mongo:</p>
  
  <blockquote>
    <p>For now, you must already have your application running locally with meteor run. This will be easier >in the future.</p>
  </blockquote>
  
  <p>Is this what they mean?</p>
  
  <p>Obviously, it is isn't crucial that I have shell access from meteor to my local instance since I can always get shell access by just typing mongo, but my concern has to do with deployment, and should I want shell access then, this might be a problem.</p>