Merge branch 'main' into args-tests

Author: blva

.github/dependabot.yml

@@ -4,6 +4,22 @@ updates:
     directory: "/"
     schedule:
       interval: "weekly"
+    ignore:
+      # We are ignoring major updates on yargs-parser because yargs-parser@22
+      # does not play nicely when bundled using webpack. Our VSCode extension
+      # bundles MCP server with the extension code and yargs-parser from MCP
+      # server ends up on the final bundle which leads to issues such as -
+      # https://github.com/mongodb-js/vscode/issues/1149.
+      #
+      # This was reported to yargs-parser as well -
+      # https://github.com/yargs/yargs-parser/issues/517 and we already tried
+      # their suggestion about disabling the meta resolution in webpack,
+      # alongside others (dependency overrides, disabling the bundling of
+      # yargs-parser), and none of the solutions yield a working extension. So
+      # until we figure out a fix for this we need to keep mongodb-mcp-server
+      # working with v21 of yargs-parser.
+      - dependency-name: "yargs-parser"
+        update-types: ["version-update:semver-major"]
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:

.github/workflows/code-health-fork.yml

@@ -20,6 +20,11 @@ jobs:
       - uses: GitHubSecurityLab/actions-permissions/monitor@v1
         if: matrix.os == 'ubuntu-latest'
       - uses: actions/checkout@v5
+      - uses: docker/setup-docker-action@v4
+        if: matrix.os == 'ubuntu-latest'
+        name: Setup Docker Environment
+        with:
+          set-host: true
       - uses: actions/setup-node@v5
         with:
           node-version-file: package.json

.github/workflows/code-health.yml

@@ -21,6 +21,11 @@ jobs:
       - uses: GitHubSecurityLab/actions-permissions/monitor@v1
         if: matrix.os == 'ubuntu-latest'
       - uses: actions/checkout@v5
+      - uses: docker/setup-docker-action@v4
+        if: matrix.os == 'ubuntu-latest'
+        name: Setup Docker Environment
+        with:
+          set-host: true
       - uses: actions/setup-node@v5
         with:
           node-version-file: package.json

.github/workflows/jira-issue.yml

@@ -54,7 +54,7 @@ jobs:
 
       - name: Add comment
         if: steps.create.outputs.issue-key
-        uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043
+        uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9
         with:
           issue-number: ${{ github.event.issue.number }}
           body: |
@@ -104,7 +104,7 @@ jobs:
           transition-id: 61
       - name: Add closure comment
         if: steps.close_jira_ticket.outcome == 'success'
-        uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043
+        uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9
         with:
           issue-number: ${{ github.event.issue.number }}
           body: |

README.md

@@ -360,6 +360,7 @@ The MongoDB MCP Server can be configured using multiple methods, with the follow
 | `exportTimeoutMs`                      | `MDB_MCP_EXPORT_TIMEOUT_MS`                         | 300000                                                                      | Time in milliseconds after which an export is considered expired and eligible for cleanup.                                                                                                              |
 | `exportCleanupIntervalMs`              | `MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS`                | 120000                                                                      | Time in milliseconds between export cleanup cycles that remove expired export files.                                                                                                                    |
 | `atlasTemporaryDatabaseUserLifetimeMs` | `MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS` | 14400000                                                                    | Time in milliseconds that temporary database users created when connecting to MongoDB Atlas clusters will remain active before being automatically deleted.                                             |
+| `voyageApiKey`                         | `MDB_VOYAGE_API_KEY`                                | <not set>                                                                   | API key for communicating with Voyage AI. Used for generating embeddings for Vector search.                                                                                                             |
 
 #### Logger Options