Connections & SSH

Your databases, together.
Your credentials, protected.

Bring local development, Atlas, and private MongoDB deployments into one sidebar. Connection testing explains the steps, and environment labels keep production in plain sight.

MongoDB AtlasBuilt-in SSH & TLSmacOS Keychain
Take a closer look

One familiar home

From localhost
to your next deployment.

Local development

Your next idea starts here.

MongoDB Atlas

Your cloud database, close by.

Behind SSH

A built-in path to private data.

Bison Credentials in Keychain
Illustration of supported connection workflows.
01

Paste a URI. Or use the form.

Connection strings and form fields stay in sync. Use mongodb:// or mongodb+srv:// for direct connections, with SCRAM and TLS options.

02

Reach private deployments.

Use a built-in SSH tunnel with a password or private key. Review the server’s host-key fingerprint before trusting a new SSH server.

03

Make environments unmistakable.

Organize connections with folders and colors. Production writes always require confirmation; read-only connections refuse writes from both people and agents.

From first click to useful work

A place for
your next step.

  1. 01

    Add the connection

    Paste the MongoDB URI and choose TLS or SSH settings for the deployment.

  2. 02

    Test each step

    Check resolution, connectivity, and authentication, with explanations for common connection failures.

  3. 03

    Give it a clear home

    Name it, choose its folder and environment, and set read-only or agent access as appropriate.

A few practical details

Good to know.
Before you begin.

Where are passwords stored?

Passwords and SSH key passphrases live in macOS Keychain, separate from the saved connection metadata.

Can I use every SSH configuration option?

The built-in tunnel supports password or key authentication and selected host settings from a chosen SSH config file. ssh-agent, ProxyJump, ProxyCommand, and SRV URIs through a tunnel are not supported in the Mac App Store build.