update readme to fix docker (#40)

* update readme to fix docker

* prioritize docker

Author: jssmith

README.md

@@ -72,22 +72,34 @@ Postgres Pro includes an expanding set of tools covering several areas:
 
 Before getting started, ensure you have:
 1. Access credentials for your database.
-2. Python 3.12 or higher *or* Docker.
+2. Docker *or* Python 3.12 or higher.
+
 #### Access Credentials
  You can confirm your access credentials are valid by using `psql` or a GUI tool such as [pgAdmin](https://www.pgadmin.org/).
 
 
-#### Python or Docker
+#### Docker or Python
 
 The choice to use Docker or Python is yours.
-We generally recommend using whichever is most familiar to you.
+We generally recommend Docker because Python users can encounter more environment-specific issues.
+However, it often makes sense to use whichever method you are most familiar with.
 
 
 ### Installation
 
 Choose one of the following methods to install Postgres Pro:
 
-#### Option 1: Using Python
+#### Option 1: Using Docker
+
+Pull the Postgres Pro MCP server Docker image.
+This image contains all necessary dependencies, providing a reliable way to run Postgres Pro in a variety of environments.
+
+```bash
+docker pull crystaldba/postgres-mcp
+```
+
+
+#### Option 2: Using Python
 
 If you have `pipx` installed you can install Postgres Pro with:
 
@@ -103,14 +115,6 @@ uv pip install postgres-mcp
 
 If you need to install `uv`, see the [uv installation instructions](https://docs.astral.sh/uv/getting-started/installation/).
 
-#### Option 2: Using Docker
-
-Pull the Postgres Pro MCP server Docker image.
-This image contains all necessary dependencies, providing a reliable way to run Postgres Pro in a variety of environments.
-
-```bash
-docker pull crystaldba/postgres-mcp
-```
 
 ### Configure Your AI Assistant
 
@@ -128,14 +132,20 @@ You can also use `Settings` menu item in Claude Desktop to locate the configurat
 
 You will now edit the `mcpServers` section of the configuration file.
 
-##### If you are using `pipx`
+##### If you are using Docker
 
 ```json
 {
   "mcpServers": {
     "postgres": {
-      "command": "postgres-mcp",
+      "command": "docker",
       "args": [
+        "run",
+        "-i",
+        "--rm",
+        "-e",
+        "DATABASE_URI",
+        "crystaldba/postgres-mcp",
         "--access-mode=unrestricted"
       ],
       "env": {
@@ -146,16 +156,20 @@ You will now edit the `mcpServers` section of the configuration file.
 }
 ```
 
-##### If you are using `uv`
+The Postgres Pro Docker image will automatically remap the hostname `localhost` to work from inside of the container.
+
+- MacOS/Windows: Uses `host.docker.internal` automatically
+- Linux: Uses `172.17.0.1` or the appropriate host address automatically
+
+
+##### If you are using `pipx`
 
 ```json
 {
   "mcpServers": {
     "postgres": {
-      "command": "uv",
+      "command": "postgres-mcp",
       "args": [
-        "run",
-        "postgres-mcp",
         "--access-mode=unrestricted"
       ],
       "env": {
@@ -166,19 +180,17 @@ You will now edit the `mcpServers` section of the configuration file.
 }
 ```
 
-##### If you are using Docker
+
+##### If you are using `uv`
 
 ```json
 {
   "mcpServers": {
     "postgres": {
-      "command": "docker",
+      "command": "uv",
       "args": [
         "run",
-        "--rm",
-        "-e",
-        "DATABASE_URI",
-        "crystaldba/postgres-mcp",
+        "postgres-mcp",
         "--access-mode=unrestricted"
       ],
       "env": {
@@ -189,34 +201,11 @@ You will now edit the `mcpServers` section of the configuration file.
 }
 ```
 
-The Postgres Pro Docker image will automatically remap the hostname `localhost` to work from inside of the container.
-
-- MacOS/Windows: Uses `host.docker.internal` automatically
-- Linux: Uses `172.17.0.1` or the appropriate host address automatically
-
 
 ##### Connection URI
 
 Replace `postgresql://...` with your [Postgres database connection URI](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS).
 
-You can also use `psql`-style connection parameters:
-
-```json
-{
-  "mcpServers": {
-    "postgres": {
-      "command": "postgres-mcp",
-      "args": [
-        "-h", "localhost",
-        "-p", "5432",
-        "-U", "username",
-        "-d", "dbname",
-        "--access-mode=unrestricted"
-      ]
-    }
-  }
-}
-```
 
 ##### Access Mode
 
@@ -314,7 +303,7 @@ Postgres Pro Tools:
 
 **Postgres MCP Servers**
 - [Query MCP](https://github.com/alexander-zuev/supabase-mcp-server). An MCP server for Supabase Postgres with a three-tier safety architecture and Supabase management API support.
-- [PG-MCP](https://github.com/stuzero/pg-mcp). An MCP server for PostgreSQL with flexible connection options, explain plans, extension context, and more.
+- [PG-MCP](https://github.com/stuzero/pg-mcp-server). An MCP server for PostgreSQL with flexible connection options, explain plans, extension context, and more.
 - [Reference PostgreSQL MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/postgres). A simple MCP Server implementation exposing schema information as MCP resources and executing read-only queries.
 - [Supabase Postgres MCP Server](https://github.com/supabase-community/supabase-mcp). This MCP Server provides Supabase management features and is actively maintained by the Supabase community.
 - [Nile MCP Server](https://github.com/niledatabase/nile-mcp-server). An MCP server providing access to the management API for the Nile's multi-tenant Postgres service.
@@ -483,7 +472,7 @@ We remain open to revising this decision in the future.
 Like the [Reference PostgreSQL MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/postgres), Postgres Pro takes Postgres connection information at startup.
 This is convenient for users who always connect to the same database but can be cumbersome when users switch databases.
 
-An alternative approach, taken by [PG-MCP](https://github.com/stuzero/pg-mcp), is provide connection details via MCP tool calls at the time of use.
+An alternative approach, taken by [PG-MCP](https://github.com/stuzero/pg-mcp-server), is provide connection details via MCP tool calls at the time of use.
 This is more convenient for users who switch databases, and allows a single MCP server to simultaneously support multiple end-users.
 
 There must be a better approach than either of these.