feat: add Atlas Stream Processing tools MCP-406 by jwongmongodb · Pull Request #967 · mongodb-js/mongodb-mcp-server

jwongmongodb · 2026-03-11T23:41:44Z

Summary

Adds 4 new MCP tools (atlas-streams-discover, atlas-streams-build, atlas-streams-manage, atlas-streams-teardown) covering the full lifecycle of Atlas Stream Processing resources:

discover — list/inspect workspaces, connections, processors; fetch logs and networking; diagnose processor health
build — create workspaces, connections (Kafka, HTTPS, S3, Schema Registry, cluster, etc.), processors with pipeline definitions, and PrivateLink endpoints
manage — start/stop/modify processors, update workspaces (tier, region), update connections, accept/reject VPC peering
teardown — delete processors, connections, workspaces, PrivateLink endpoints, and VPC peering

Includes shared base class (StreamsToolBase) with common validation, elicitation flows for destructive confirmations, and reusable argument schemas.

Companion PR: This should be used with the agent skill defined in mongodb/agent-skills#10, which provides the LLM with streaming-specific guidance for using these tools effectively.

Test plan

Unit tests pass (171 tests across 6 suites)
Integration tests pass (45 tests against live Atlas)
Type check, lint, format, dependencies all pass
CI passes on this PR

🤖 Generated with Claude Code

jwongmongodb · 2026-03-11T23:48:34Z

Question: Integration test scope — is this overkill? @blva

The integration tests in this PR cover 40 scenarios including workspace CRUD, connection CRUD (HTTPS, Kafka, Schema Registry), processor lifecycle (create, start, stop, modify, delete), workspace tier updates, networking, logs, and cross-workspace discovery.

For comparison, the terraform-provider-mongodbatlas repo — which has dedicated CI infrastructure — covers a similar scope across its streams integration tests:

Stream instances: basic CRUD + stream config tiers (~2 tests)
Stream connections: Kafka (plaintext, OAuth, SSL, VPC networking), cluster, sample, HTTPS, Lambda, Schema Registry, PrivateLink (~13 tests)
Stream processors: basic CRUD, tier changes, state transitions, options, cluster type, error cases, timeouts (~10 tests)
PrivateLink endpoints: Confluent, MSK, S3 (~6 tests)

Our MCP server integration tests overlap significantly with that coverage (workspace CRUD, Kafka/SchemaRegistry/HTTPS connections, processor lifecycle, tier changes). A few things we don't cover that the terraform provider does: VPC/PrivateLink networking, Lambda connections, S3 connections, OAuth auth — but those require external cloud infrastructure.

Questions for the team:

Is the current level of integration test coverage overkill for this repo, or is this the right level of rigor?
Should we lean more on unit tests and keep integration tests to a minimal smoke-test set (e.g., just workspace + connection CRUD), given the terraform provider already exercises the Atlas API thoroughly?
Are there concerns about integration test runtime/cost with 40 tests hitting live Atlas?

coveralls · 2026-03-11T23:49:51Z

Pull Request Test Coverage Report for Build 23150993685

Details

1927 of 1982 (97.23%) changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.7%) to 84.926%

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/tools/atlas/streams/streamsToolBase.ts	160	162	98.77%
src/tools/atlas/streams/teardown.ts	206	211	97.63%
src/tools/atlas/streams/build.ts	616	639	96.4%
src/tools/atlas/streams/discover.ts	491	516	95.16%

Totals
Change from base Build 23143087931:	2.7%
Covered Lines:	10359
Relevant Lines:	11946

💛 - Coveralls

jwongmongodb · 2026-03-11T23:48:02Z

src/common/schemas.ts

@@ -1,4 +1,4 @@
-export const previewFeatureValues = ["search", "mcpUI"] as const;
+export const previewFeatureValues = ["search", "mcpUI", "streams"] as const;


this will be removed after the PR to add the Accuracy test is created.

jwongmongodb · 2026-03-12T00:07:07Z

src/common/config/userConfig.ts

            "drop-collection",
            "delete-many",
            "drop-index",
+            "atlas-streams-manage",


this is needed for elicitation to the users that modifies or deletes their streams resources.

jwongmongodb · 2026-03-12T02:44:31Z

@blva I tagged you for an initial review so you can get an early look before my next pass tomorrow morning at this PR. I also have some early questions about the Integration testing philosophy in the above comment.

blva · 2026-03-12T11:57:16Z

Question: Integration test scope — is this overkill? @blva

The integration tests in this PR cover 40 scenarios including workspace CRUD, connection CRUD (HTTPS, Kafka, Schema Registry), processor lifecycle (create, start, stop, modify, delete), workspace tier updates, networking, logs, and cross-workspace discovery.

For comparison, the terraform-provider-mongodbatlas repo — which has dedicated CI infrastructure — covers a similar scope across its streams integration tests:

Stream instances: basic CRUD + stream config tiers (~2 tests)

Stream connections: Kafka (plaintext, OAuth, SSL, VPC networking), cluster, sample, HTTPS, Lambda, Schema Registry, PrivateLink (~13 tests)

Stream processors: basic CRUD, tier changes, state transitions, options, cluster type, error cases, timeouts (~10 tests)

PrivateLink endpoints: Confluent, MSK, S3 (~6 tests)

Our MCP server integration tests overlap significantly with that coverage (workspace CRUD, Kafka/SchemaRegistry/HTTPS connections, processor lifecycle, tier changes). A few things we don't cover that the terraform provider does: VPC/PrivateLink networking, Lambda connections, S3 connections, OAuth auth — but those require external cloud infrastructure.

Questions for the team:

Is the current level of integration test coverage overkill for this repo, or is this the right level of rigor?

Should we lean more on unit tests and keep integration tests to a minimal smoke-test set (e.g., just workspace + connection CRUD), given the terraform provider already exercises the Atlas API thoroughly?

Are there concerns about integration test runtime/cost with 40 tests hitting live Atlas?

Hi, this is about testing our integration with the Streams API works well. Terraform uses a different SDK and codebase. We should include int tests in my opinion. I'm OK with a second PR if this one is already too big.

jwongmongodb · 2026-03-12T11:59:45Z

Hi, this is about testing our integration with the Streams API works well. Terraform uses a different SDK and codebase. We should include int tests in my opinion. I'm OK with a second PR if this one is already too big.

Okay, I'll add those integration tests in the PR Accuracy test as well if that is okay. Since this has the preview flag on it, it should be enough guardrails before the final PR is merged.

src/telemetry/types.ts

src/tools/atlas/streams/discover.ts

jwongmongodb · 2026-03-12T13:47:09Z

tests/integration/tools/mongodb/delete/dropIndex.test.ts

+                                mode: "form",
+                                requestedSchema: Elicitation.CONFIRMATION_SCHEMA,
+                            },
+                            { timeout: 300000 }


this is from the elicitation timeout addition

jwongmongodb · 2026-03-12T13:51:58Z

tests/integration/tools/atlas/streams/build.test.ts

+        // - S3 connection creation (requires AWS IAM role ARN registered in Atlas)
+        // - AWSKinesisDataStreams connection creation (requires AWS IAM role ARN)
+        // - AWSLambda connection creation (requires AWS IAM role ARN)
+        // - PrivateLink creation (requires provider-specific infrastructure)


These private link connections can take up to 10 minutes to provision, is it okay to have our integration tests running for that long? For reference, the integration tests in the terraform provider for streams can take up to 35 to 40 minutes.

great point! lets have them running in Code Health Long Running Tests, performance advisor tests also run there

left a comment mentioning where you can add it (#967 (comment))

jwongmongodb · 2026-03-12T13:53:08Z

src/elicitation.ts

+    | { accepted: true; fields: Record<string, string> }
+    | { accepted: false; fields?: undefined };
+
+const ELICITATION_TIMEOUT_MS = 300_000; // 5 minutes for user interaction


The timeout was added to the existing confirmAction method in elicitation.ts — the server.elicitInput() call previously had no timeout, which means it would use the SDK's default (which could hang indefinitely if a client never responds). We added { timeout: 300_000 } (5 minutes) to give users reasonable time to respond while preventing the server from hanging forever.

tests/integration/tools/atlas/streams/manage.test.ts

src/tools/atlas/streams/streamsToolBase.ts

src/tools/atlas/streams/discover.ts

blva · 2026-03-12T14:15:22Z

src/tools/atlas/streams/discover.ts

+                              : {},
+                      },
+                      headers: {
+                          Accept: "application/vnd.atlas.2025-03-12+gzip",


we should handle the versions in the api client layer, hardcoding the version in the tool is very error prone. if you extend that functionality, that can be in a new PR so that it's easy to revert if changes separately if any bugs show up.

Agreed, the versions shouldn't be hardcoded in the tool. The top of apiClient.ts (client setup, middleware, etc.) is hand-written, only the wrapper methods below line 210 are auto-generated. So we could add middleware there that sets the right Accept header for gzip endpoints. I'll pull this out into a follow-up PR to keep it easy to revert separately.

src/tools/atlas/streams/discover.ts

Copilot

Pull request overview

Adds Atlas Stream Processing (“streams”) support to the MCP server by introducing four new Atlas tools (discover/build/manage/teardown), shared streams utilities/base class, and extending elicitation + tests/config/docs to support the new workflows.

Changes:

Add new Atlas Streams tools (atlas-streams-discover, atlas-streams-build, atlas-streams-manage, atlas-streams-teardown) plus shared StreamsToolBase and StreamsArgs.
Extend elicitation to support structured form input (with timeout), and update unit/integration tests accordingly.
Add streams integration test helpers/workflows and wire streams into telemetry, preview features, config defaults, and README.

Reviewed changes

Copilot reviewed 32 out of 32 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
vitest.config.ts	Adjusts Atlas test skipping behavior via `SKIP_ATLAS_TESTS` exclusion glob.
tests/utils/elicitationMocks.ts	Generalizes mock elicitation content typing to support structured input.
tests/unit/tools/atlas/streams/teardown.test.ts	Unit coverage for teardown behaviors (processors/connections/workspaces/networking deletes).
tests/unit/tools/atlas/streams/streamsToolBase.test.ts	Unit coverage for streams-specific error handling, telemetry metadata, and connection-name extraction.
tests/unit/tools/atlas/streams/streamsArgs.test.ts	Unit coverage for streams name validation schemas.
tests/unit/tools/atlas/streams/manage.test.ts	Unit coverage for manage actions (start/stop/modify/update/peering).
tests/unit/tools/atlas/streams/discover.test.ts	Unit coverage for discover actions (list/inspect/diagnose/logs/networking).
tests/unit/tools/atlas/streams/build.test.ts	Unit coverage for build resources (workspace/connection/processor/privatelink) and validation/elicitation flows.
tests/unit/elicitation.test.ts	Adds/updates tests for timeout + new `requestInput()` structured elicitation method.
tests/unit/common/config.test.ts	Updates default confirmation-required tools list to include streams manage/teardown.
tests/integration/tools/mongodb/delete/dropIndex.test.ts	Updates integration expectations to include elicitation timeout arg.
tests/integration/tools/atlas/streams/workflow.test.ts	End-to-end streams workflow tests covering build/discover/manage/teardown.
tests/integration/tools/atlas/streams/teardown.test.ts	Validates teardown tool registration + basic deletion flow.
tests/integration/tools/atlas/streams/manage.test.ts	Validates manage tool registration + processor lifecycle actions.
tests/integration/tools/atlas/streams/discover.test.ts	Validates discover tool registration and common actions against live Atlas.
tests/integration/tools/atlas/streams/build.test.ts	Validates build tool registration and common connection creation flows.
tests/integration/tools/atlas/atlasHelpers.ts	Adds `describeWithStreams` + `withWorkspace` provisioning helper (workspace + cluster + connections).
tests/integration/elicitation.test.ts	Updates integration expectations to include elicitation timeout arg.
tests/browser/vitest.config.ts	Adds `node:zlib` alias for browser tests.
tests/browser/polyfills/zlib/index.ts	Adds `gunzipSync` polyfill stub to satisfy imports.
src/tools/atlas/tools.ts	Exports the new streams tools from the Atlas tools index.
src/tools/atlas/streams/teardown.ts	Implements `atlas-streams-teardown` tool and confirmation messaging.
src/tools/atlas/streams/streamsToolBase.ts	Adds streams-specific feature gating, error hints, connection-name extraction, telemetry metadata.
src/tools/atlas/streams/streamsArgs.ts	Adds shared Zod schemas for streams resource naming.
src/tools/atlas/streams/manage.ts	Implements `atlas-streams-manage` tool (processor/workspace/connection/peering operations).
src/tools/atlas/streams/discover.ts	Implements `atlas-streams-discover` tool (list/inspect/diagnose/logs/networking).
src/tools/atlas/streams/build.ts	Implements `atlas-streams-build` tool with validation and structured elicitation for missing config.
src/telemetry/types.ts	Adds `StreamsToolMetadata` and includes it in tool metadata union.
src/elicitation.ts	Adds structured `requestInput()` + introduces a standard 5-minute timeout for elicitation calls.
src/common/schemas.ts	Adds `streams` to preview features.
src/common/config/userConfig.ts	Adds streams manage/teardown to default confirmation-required tools list.
README.md	Documents new tools, streams preview feature, and updates config defaults/roles table.

vitest.config.ts

src/tools/atlas/streams/discover.ts

src/tools/atlas/streams/build.ts

src/tools/atlas/streams/teardown.ts

tests/browser/polyfills/zlib/index.ts

README.md

src/tools/atlas/streams/build.ts

src/tools/atlas/streams/manage.ts

tests/integration/tools/atlas/atlasHelpers.ts

vitest.config.ts

blva · 2026-03-12T19:36:15Z

vitest.config.ts

@@ -13,7 +13,7 @@ const vitestDefaultExcludes = [
 const longRunningTests = ["tests/integration/tools/atlas/performanceAdvisor.test.ts"];


this is where you should add your test as longRunning

@jwongmongodb i think you missed this comment about adding your test to the long running tests?

ah, I misunderstood, I thought the new long running test to be added later will be added here, the current tests are quick. Do you want me to move all the tests here right now (even the current quick ones)?

My comment was for the todo tests to come in the next PR (private link etc)

oh, I see! I meant only the integration tests that take some time (e.g. creating takes long, etc)

yep, I think the current tests are quite fast, so I will have the long running ones here in the next PR. I'll fix the cleanup now

README.md

Copilot

Pull request overview

Copilot reviewed 36 out of 36 changed files in this pull request and generated 5 comments.

src/tools/atlas/streams/build.ts

src/tools/atlas/tools.ts

src/tools/atlas/streams/manage.ts

src/tools/atlas/streams/teardown.ts

Copilot

Pull request overview

Copilot reviewed 36 out of 36 changed files in this pull request and generated 3 comments.

src/tools/atlas/streams/build.ts

jwongmongodb · 2026-03-13T17:40:22Z

src/tools/atlas/streams/discover.ts

+        try {
+            const buffer = Buffer.from(data as unknown as ArrayBuffer);
+            const decompressed = gunzipSync(buffer).toString("utf-8");
+
+            // Limit output to avoid overwhelming the context
+            const lines = decompressed.split("\n").filter((line) => line.trim());
+            const maxLines = 100;
+            const truncated = lines.length > maxLines;
+            const output = lines.slice(-maxLines).join("\n");


gunzipSync on a bounded API response is fine in practice, the MCP server is single-client, the Atlas API caps log payloads, and the output is truncated to 100 lines regardless. The async swap is a marginal improvement for a scenario that's unlikely to cause real issues.

wdym by single-client? MCP handles multiple connections via streamable HTTP, there are use-cases where users deploy it in hosts and have multiple clients connecting.

You're right, that was an incorrect assumption on my part. I was thinking in terms of stdio transport (which is single-client), but with streamable HTTP the server handles multiple concurrent connections. I'll swap to async gunzip to avoid blocking the event loop. (I'll push the fix tmr morning my time.)

src/tools/atlas/tools.ts

src/tools/atlas/streams/build.ts

src/tools/atlas/streams/teardown.ts

…etry Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…Id describe, add CLOUDP ticket Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…ce readiness loop

…kspace deletion in tests

…g project

…descriptions and error flags - Validate resourceName/peeringId/workspaceName in getConfirmationMessage() before interpolation to prevent 'undefined' in confirmation prompts (manage.ts, teardown.ts) - Add isError: true to missingFieldsResponse() in build.ts so failed validation is correctly reported as an error - Fix connectionConfig description to reflect Sample needing no config and partial config being valid via elicitation - Fix teardown description to accurately reflect safety check behavior - Add unit tests for missing-field validation in confirmation messages Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

validateSchemaRegistryConfig always defaulted auth type to USER_INFO and required username/password, even when SASL_INHERIT was specified. SASL_INHERIT inherits credentials from a Kafka connection and does not need explicit username/password. Skip credential checks when auth type is SASL_INHERIT. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…P connections

…t running processors in teardown warning

cveticm

LGTM! Thanks for the changes!

jwongmongodb changed the title ~~feat(streams): add Atlas Stream Processing MCP tools~~ feat: add Atlas Stream Processing tools MCP-406 Mar 11, 2026

jwongmongodb force-pushed the atlas-streams-tools branch from af3bfff to e16d079 Compare March 11, 2026 23:46

jwongmongodb force-pushed the atlas-streams-tools branch from d8ec8c9 to cd1675c Compare March 12, 2026 00:56

jwongmongodb commented Mar 12, 2026

View reviewed changes

jwongmongodb requested a review from blva March 12, 2026 02:43

jwongmongodb force-pushed the atlas-streams-tools branch 2 times, most recently from a9bde70 to d1778b9 Compare March 12, 2026 13:38

blva reviewed Mar 12, 2026

View reviewed changes

src/telemetry/types.ts Outdated Show resolved Hide resolved

blva reviewed Mar 12, 2026

View reviewed changes

src/tools/atlas/streams/discover.ts Outdated Show resolved Hide resolved

jwongmongodb commented Mar 12, 2026

View reviewed changes

blva reviewed Mar 12, 2026

View reviewed changes

src/tools/atlas/streams/streamsToolBase.ts Show resolved Hide resolved

blva reviewed Mar 12, 2026

View reviewed changes

src/tools/atlas/streams/discover.ts Outdated Show resolved Hide resolved

blva reviewed Mar 12, 2026

View reviewed changes

src/tools/atlas/streams/discover.ts Outdated Show resolved Hide resolved

jwongmongodb force-pushed the atlas-streams-tools branch 2 times, most recently from ac0fa56 to fd0a797 Compare March 12, 2026 19:08

jwongmongodb requested a review from blva March 12, 2026 19:26

jwongmongodb marked this pull request as ready for review March 12, 2026 19:26

jwongmongodb requested a review from a team as a code owner March 12, 2026 19:26

Copilot AI review requested due to automatic review settings March 12, 2026 19:26

Copilot started reviewing on behalf of jwongmongodb March 12, 2026 19:26 View session

Copilot AI reviewed Mar 12, 2026

View reviewed changes

blva reviewed Mar 12, 2026

View reviewed changes

vitest.config.ts Show resolved Hide resolved

blva reviewed Mar 12, 2026

View reviewed changes

README.md Outdated Show resolved Hide resolved

Copilot AI reviewed Mar 13, 2026

View reviewed changes

jwongmongodb requested a review from Copilot March 13, 2026 17:00

Copilot started reviewing on behalf of jwongmongodb March 13, 2026 17:01 View session

Copilot AI reviewed Mar 13, 2026

View reviewed changes

cveticm reviewed Mar 16, 2026

View reviewed changes

src/tools/atlas/streams/build.ts Outdated Show resolved Hide resolved

cveticm reviewed Mar 16, 2026

View reviewed changes

src/tools/atlas/streams/teardown.ts Outdated Show resolved Hide resolved

jwongmongodb and others added 17 commits March 16, 2026 10:03

feat: add atlas-streams-discover tool

d6b816f

feat: add atlas-streams-build tool

155c541

feat: add atlas-streams-manage tool

120c54a

feat: add atlas-streams-teardown tool

ca7ec77

test: add cross-tool workflow integration tests

543d993

fix: address PR review — deduplicate error handlers, remove PII telem…

00e0375

…etry Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: address PR review — remove find/list-all-processors, fix project…

8ef6217

…Id describe, add CLOUDP ticket Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix: regenerate README to remove find-processor and list-all-processors

2d0efc9

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

refactor: rename SKIP_ATLAS_TESTS to SKIP_ATLAS_INTEGRATION_TESTS

6735f6c

fix: correct descriptions, add tier z.enum validation, harden workspa…

3747b80

…ce readiness loop

fix: make gunzipSync polyfill return input buffer instead of undefined

b74eb35

fix: add streams workspace cleanup to cleanup script and wait for wor…

46469bc

…kspace deletion in tests

fix: parallelize cleanup and wait for cluster deletion before deletin…

afdb691

…g project

fix: use async gunzip to avoid blocking event loop with concurrent MC…

7e60d80

…P connections

fix: add missing metrics mock to streams test files after rebase

82e7842

jwongmongodb force-pushed the atlas-streams-tools branch 2 times, most recently from df6a241 to 82e7842 Compare March 16, 2026 14:37

fix: prevent privateLinkConfig from overwriting provider and only lis…

3f75134

…t running processors in teardown warning

jwongmongodb requested a review from cveticm March 16, 2026 15:16

cveticm approved these changes Mar 16, 2026

View reviewed changes

jwongmongodb merged commit 811835b into main Mar 16, 2026
20 checks passed

jwongmongodb deleted the atlas-streams-tools branch March 16, 2026 18:42

		@@ -1,4 +1,4 @@
		export const previewFeatureValues = ["search", "mcpUI"] as const;
		export const previewFeatureValues = ["search", "mcpUI", "streams"] as const;

		@@ -13,7 +13,7 @@ const vitestDefaultExcludes = [
		const longRunningTests = ["tests/integration/tools/atlas/performanceAdvisor.test.ts"];

Conversation

jwongmongodb commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

jwongmongodb commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coveralls commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Test Coverage Report for Build 23150993685

Details

💛 - Coveralls

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jwongmongodb commented Mar 12, 2026

Uh oh!

blva commented Mar 12, 2026

Uh oh!

jwongmongodb commented Mar 12, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

blva Mar 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jwongmongodb Mar 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

jwongmongodb commented Mar 11, 2026 •

edited

Loading

jwongmongodb commented Mar 11, 2026 •

edited

Loading

coveralls commented Mar 11, 2026 •

edited

Loading

blva Mar 12, 2026 •

edited

Loading

jwongmongodb Mar 13, 2026 •

edited

Loading