changing GHA to only run on push to main. updating readme

Author: launchdavewilliams

.github/workflows/docker_build_and_push.yaml

@@ -1,6 +1,8 @@
 name: Docker Build and Push
 on:
   push:
+    branches:
+      - main
 
 env:
   ECR_REGISTRY: "709825985650.dkr.ecr.us-east-1.amazonaws.com/launchdarkly/mcp"

README.md

@@ -143,6 +143,36 @@ Some AI clients allow for accessing environment variables within MCP configurati
 }
 ```
 
+### Installation steps for Docker
+
+If installing the MCP server from the AWS Markeplace, pull the image using an authenticated role using the provided instructions in the marketplace listing.
+
+To run the container:
+
+```bash
+docker run --rm -p 8080:8080 709825985650.dkr.ecr.us-east-1.amazonaws.com/launchdarkly/mcp --api-key api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 
+```
+
+Then, configure your server definition to reference your local clone. For example:
+
+```json
+{
+  "mcpServers": {
+    "launchdarkly": {
+      "command": "npx",
+      "args": [
+        "-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start",
+        "--api-key", "$LD_ACCESS_TOKEN"
+      ],
+      "env": {
+        "LD_ACCESS_TOKEN": "MCP_LD_TOKEN"
+      }
+      "url": "http://localhost:8080/sse"
+    }
+  }
+}
+```
+
 This won't work in AI clients (such as Cursor) which don't support accessing environment variables directly within MCP configurations. As a workaround, you can invoke a local script from your MCP configuration. See [here](https://github.com/launchdarkly/mcp-server/issues/26#issuecomment-3064419507) for an example.
 
 <!-- Start Requirements [requirements] -->