mongodb-mcp-server 0.2.0 → 0.3.1-prerelease.1

package/.github/workflows/jira-issue.yml

@@ -1,72 +0,0 @@
----
-name: Create JIRA ticket for new issues
-
-on:
-  issues:
-    types: [opened, labeled]
-
-permissions:
-  issues: write
-  contents: read
-
-jobs:
-  jira_task:
-    name: Create Jira issue
-    runs-on: ubuntu-latest
-    if: github.event.action == 'opened' || github.event.label.name == 'create-jira'
-    steps:
-      - uses: GitHubSecurityLab/actions-permissions/monitor@v1
-        with:
-          config: ${{ vars.PERMISSIONS_CONFIG }}
-
-      - name: Create JIRA ticket
-        uses: mongodb/apix-action/create-jira@v8
-        id: create
-        continue-on-error: true
-        with:
-          token: ${{ secrets.JIRA_API_TOKEN }}
-          project-key: MCP
-          summary: "HELP: GitHub Issue n. ${{ github.event.issue.number }}"
-          issuetype: Bug
-          description: "This ticket tracks the following GitHub issue: ${{ github.event.issue.html_url }}."
-          extra-data: |
-            {
-              "fields": {
-                "customfield_12751": [
-                  {
-                    "id": "22223"
-                  },
-                  {
-                    "id": "27326"
-                  }
-                ]
-              }
-            }
-      - name: Show result
-        run: |
-          echo "JIRA action result: ${{ steps.create.outputs.issue-key || 'FAILED' }}"
-
-      - name: Add comment
-        if: steps.create.outputs.issue-key
-        uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043
-        with:
-          issue-number: ${{ github.event.issue.number }}
-          body: |
-            Thanks for opening this issue. The ticket [${{ steps.create.outputs.issue-key }}](https://jira.mongodb.org/browse/${{ steps.create.outputs.issue-key }}) was created for internal tracking.
-
-      - name: Remove create-jira label
-        if: github.event.action == 'labeled' && github.event.label.name == 'create-jira'
-        uses: actions/github-script@v7
-        with:
-          script: |
-            try {
-              await github.rest.issues.removeLabel({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
-                name: 'create-jira'
-              });
-              console.log('✅ Removed create-jira label');
-            } catch (error) {
-              console.log('⚠️ Could not remove create-jira label:', error.message);
-            }

package/.github/workflows/prepare_release.yaml

@@ -1,53 +0,0 @@
-name: Prepare release
-description: |
-  Bumps the version in package.json and creates a release PR. Once merged, the new
-  version will be published to npm.
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: "Exact version to bump to or one of major, minor, patch"
-        required: true
-        default: "patch"
-
-permissions: {}
-
-jobs:
-  create-pr:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: GitHubSecurityLab/actions-permissions/monitor@v1
-      - uses: mongodb-js/devtools-shared/actions/setup-bot-token@main
-        id: app-token
-        with:
-          app-id: ${{ vars.DEVTOOLS_BOT_APP_ID }}
-          private-key: ${{ secrets.DEVTOOLS_BOT_PRIVATE_KEY }}
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: package.json
-          registry-url: "https://registry.npmjs.org"
-          cache: "npm"
-      - name: Bump version
-        id: bump-version
-        run: |
-          echo "NEW_VERSION=$(npm version ${{ inputs.version }} --no-git-tag-version)" >> $GITHUB_OUTPUT
-      - name: Create release PR
-        uses: peter-evans/create-pull-request@271a8d0340265f705b14b6d32b9829c1cb33d45e # 7.0.8
-        id: create-pr
-        with:
-          title: "chore: release ${{ steps.bump-version.outputs.NEW_VERSION }}"
-          token: ${{ steps.app-token.outputs.token }}
-          commit-message: "chore: release ${{ steps.bump-version.outputs.NEW_VERSION }}"
-          body: |
-            This PR bumps the package version to ${{ steps.bump-version.outputs.NEW_VERSION }}.
-            Once merged, the new version will be published to npm.
-          base: main
-          branch: chore_release_${{ steps.bump-version.outputs.NEW_VERSION }}
-          author: "${{ steps.app-token.outputs.app-slug}}[bot] <${{ steps.app-token.outputs.app-email }}>"
-          committer: "${{ steps.app-token.outputs.app-slug}}[bot] <${{ steps.app-token.outputs.app-email }}>"
-      - name: Set auto merge
-        env:
-          GH_TOKEN: ${{ steps.app-token.outputs.token }}
-        run: |
-          gh pr merge ${{ steps.create-pr.outputs.pull-request-number }} --auto --squash

package/.github/workflows/publish.yaml

@@ -1,73 +0,0 @@
----
-name: Publish
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  check:
-    runs-on: ubuntu-latest
-    permissions: {}
-    outputs:
-      VERSION_EXISTS: ${{ steps.check-version.outputs.VERSION_EXISTS }}
-      VERSION: ${{ steps.get-version.outputs.VERSION }}
-    steps:
-      - uses: GitHubSecurityLab/actions-permissions/monitor@v1
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: package.json
-          registry-url: "https://registry.npmjs.org"
-          cache: "npm"
-      - name: Get version
-        id: get-version
-        shell: bash
-        run: |
-          set +e
-
-          VERSION=v$(jq -r '.version' < package.json)
-          echo "VERSION=${VERSION}" >> "$GITHUB_OUTPUT"
-      - name: Check if version already exists
-        id: check-version
-        shell: bash
-        run: |
-          set +e
-
-          git rev-parse "${{ steps.get-version.outputs.VERSION }}" >/dev/null 2>&1
-          if [[ $? -eq 0 ]]; then
-            echo "VERSION_EXISTS=true" >> "$GITHUB_OUTPUT"
-          else
-            echo "VERSION_EXISTS=false" >> "$GITHUB_OUTPUT"
-          fi
-  publish:
-    runs-on: ubuntu-latest
-    environment: Production
-    permissions:
-      contents: write
-    needs:
-      - check
-    if: needs.check.outputs.VERSION_EXISTS == 'false'
-    steps:
-      - uses: GitHubSecurityLab/actions-permissions/monitor@v1
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: package.json
-          registry-url: "https://registry.npmjs.org"
-          cache: "npm"
-      - name: Build package
-        run: |
-          npm ci
-          npm run build
-      - name: Publish to NPM
-        run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-      - name: Publish git release
-        env:
-          GH_TOKEN: ${{ github.token }}
-        run: |
-          gh release create ${{ needs.check.outputs.VERSION }} --title "${{ needs.check.outputs.VERSION }}" --generate-notes --target ${{ github.sha }}

package/.github/workflows/stale.yml

@@ -1,32 +0,0 @@
----
-name: "Stale issues and PRs handler"
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: "0 0 * * *"
-
-permissions: read-all
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
-    steps:
-      - uses: GitHubSecurityLab/actions-permissions/monitor@v1
-      - uses: actions/stale@v9
-        id: stale
-        with:
-          repo-token: ${{ secrets.GITHUB_TOKEN }}
-          stale-issue-message: |
-            This issue has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!
-          stale-pr-message: |
-            This PR has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!
-          stale-issue-label: "no-issue-activity"
-          stale-pr-label: "no-pr-activity"
-          days-before-stale: 30
-          days-before-close: 30
-          exempt-all-milestones: true
-          exempt-issue-labels: "not_stale"
-          exempt-pr-labels: "not_stale"

package/.prettierignore

@@ -1,5 +0,0 @@
-dist
-coverage
-package-lock.json
-tests/tmp
-src/common/atlas/openapi.d.ts

package/.prettierrc.json

@@ -1,37 +0,0 @@
-{
-  "trailingComma": "es5",
-  "tabWidth": 4,
-  "semi": true,
-  "singleQuote": false,
-  "printWidth": 120,
-  "overrides": [
-    {
-      "files": "*.ts",
-      "options": {
-        "insertPragma": false,
-        "proseWrap": "preserve"
-      }
-    },
-    {
-      "files": "*.json",
-      "options": {
-        "tabWidth": 2,
-        "printWidth": 80
-      }
-    },
-    {
-      "files": "*.md",
-      "options": {
-        "tabWidth": 2,
-        "printWidth": 80
-      }
-    },
-    {
-      "files": ["*.yaml", "*.yml"],
-      "options": {
-        "tabWidth": 2,
-        "printWidth": 80
-      }
-    }
-  ]
-}

package/.smithery/Dockerfile

@@ -1,30 +0,0 @@
-# Generated by https://smithery.ai. See: https://smithery.ai/docs/config#dockerfile
-# ----- Build Stage -----
-FROM node:lts-alpine AS builder
-WORKDIR /app
-
-# Copy package and configuration
-COPY ../package.json ../package-lock.json ../tsconfig.json ../tsconfig.build.json ./
-
-# Copy source code
-COPY ../src ./src
-
-# Install dependencies and build
-RUN npm ci && npm run build
-
-# ----- Production Stage -----
-FROM node:lts-alpine
-
-# Copy built artifacts
-COPY --from=builder /app/dist ./dist
-
-# Copy package.json for production install
-COPY ../package.json ../package-lock.json ./
-
-# Install only production dependencies
-RUN npm ci --production --ignore-scripts
-
-# Expose no ports (stdio only)
-
-# Default command
-CMD ["node", "dist/index.js"]

package/.smithery/smithery.yaml

@@ -1,73 +0,0 @@
-# Smithery.ai configuration
-build:
-  dockerfile: Dockerfile
-  dockerBuildPath: ../
-startCommand:
-  type: stdio
-  configSchema:
-    type: object
-    properties:
-      atlasClientId:
-        type: string
-        title: Atlas Client Id
-        description: Atlas API client ID for authentication. Required for running Atlas tools.
-      atlasClientSecret:
-        type: string
-        title: Atlas Client Secret
-        description: Atlas API client secret for authentication. Required for running Atlas tools.
-      connectionString:
-        type: string
-        title: MongoDB Connection string
-        description: MongoDB connection string for direct database connections. Optional, if not set, you'll need to call the `connect` tool before interacting with MongoDB data.
-      readOnly:
-        type: boolean
-        title: Read-only
-        description: When set to true, only allows read and metadata operation types, disabling create/update/delete operations.
-        default: false
-      indexCheck:
-        type: boolean
-        title: Index Check
-        description: When set to true, enforces that query operations must use an index, rejecting queries that would perform a collection scan.
-        default: false
-  exampleConfig:
-    atlasClientId: YOUR_ATLAS_CLIENT_ID
-    atlasClientSecret: YOUR_ATLAS_CLIENT_SECRET
-    connectionString: mongodb+srv://USERNAME:PASSWORD@YOUR_CLUSTER.mongodb.net
-    readOnly: true
-    indexCheck: false
-
-  commandFunction:
-    # A function that produces the CLI command to start the MCP on stdio.
-    |-
-    (config) => {
-      const args = ['dist/index.js'];
-      if (config) {
-        if (config.atlasClientId) {
-          args.push('--apiClientId');
-          args.push(config.atlasClientId);
-        }
-
-        if (config.atlasClientSecret) {
-          args.push('--apiClientSecret');
-          args.push(config.atlasClientSecret);
-        }
-
-        if (config.readOnly) {
-          args.push('--readOnly');
-        }
-
-        if (config.connectionString) {
-          args.push('--connectionString');
-          args.push(config.connectionString);
-        }
-
-        if (config.indexCheck) {
-          args.push('--indexCheck');
-        }
-      }
-
-      return {
-        command: "node",
-        args
-      };
-    }

package/.vscode/extensions.json

@@ -1,9 +0,0 @@
-{
-  // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
-  // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
-
-  // List of extensions which should be recommended for users of this workspace.
-  "recommendations": ["vitest.explorer"],
-  // List of extensions recommended by VS Code that should not be recommended for users of this workspace.
-  "unwantedRecommendations": []
-}

package/.vscode/launch.json

@@ -1,27 +0,0 @@
-{
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "node",
-      "request": "launch",
-      "name": "Launch Tests",
-      "runtimeExecutable": "npm",
-      "runtimeArgs": ["test"],
-      "cwd": "${workspaceFolder}",
-      "envFile": "${workspaceFolder}/.env"
-    },
-    {
-      "type": "node",
-      "request": "launch",
-      "name": "Launch Program",
-      "skipFiles": ["<node_internals>/**"],
-      "runtimeExecutable": "npm",
-      "runtimeArgs": ["start"],
-      "preLaunchTask": "tsc: build - tsconfig.build.json",
-      "outFiles": ["${workspaceFolder}/dist/**/*.js"]
-    }
-  ]
-}

package/.vscode/settings.json

@@ -1 +0,0 @@
-{}

package/CONTRIBUTING.md

@@ -1,185 +0,0 @@
-# Contributing to MongoDB MCP Server
-
-Thank you for your interest in contributing to the MongoDB MCP Server project! This document provides guidelines and instructions for contributing.
-
-## Project Overview
-
-This project implements a Model Context Protocol (MCP) server for MongoDB and MongoDB Atlas, enabling AI assistants to interact with MongoDB Atlas resources through natural language.
-
-## Development Setup
-
-### Prerequisites
-
-- Node.js (v20 or later)
-- npm
-
-### Getting Started
-
-1. Clone the repository:
-
-   ```
-   git clone https://github.com/mongodb-labs/mongodb-mcp-server.git
-   cd mongodb-mcp-server
-   ```
-
-2. Install dependencies:
-
-   ```
-   npm install
-   ```
-
-3. Add the mcp server to your IDE of choice (see the [README](README.md) for detailed client integration instructions)
-   ```json
-   {
-     "mcpServers": {
-       "MongoDB": {
-         "command": "/path/to/mongodb-mcp-server/dist/index.js"
-       }
-     }
-   }
-   ```
-
-## Code Contribution Workflow
-
-1. Create a new branch for your feature or bugfix:
-
-   ```
-   git checkout -b feature/your-feature-name
-   ```
-
-2. Make your changes, following the code style of the project
-
-3. Run the inspector and double check your changes:
-
-   ```
-   npm run inspect
-   ```
-
-4. Commit your changes using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) format.
-
-## Adding tests to the MCP Server
-
-When adding new features or fixing bugs, please ensure that you also add tests to cover your changes. This helps maintain the quality and reliability of the codebase.
-
-## Running Tests
-
-The tests can be found in the `tests` directory.
-
-You can run tests using the following npm scripts:
-
-- `npm test`: Run all tests
-
-To run a specific test file or directory:
-
-```bash
-npm test -- path/to/test/file.test.ts
-npm test -- path/to/directory
-```
-
-## Troubleshooting
-
-### Restart Server
-
-- Run `npm run build` to re-build the server if you made changes to the code
-- Press `Cmd + Shift + P` and type List MCP Servers
-- Select the MCP server you want to restart
-- Select the option to restart the server
-
-### View Logs
-
-To see MCP logs, check https://code.visualstudio.com/docs/copilot/chat/mcp-servers.
-
-- Press `Cmd + Shift + P` and type List MCP Servers
-- Select the MCP server you want to see logs for
-- Select the option to view logs in the output panel
-
-### Debugging
-
-For debugging, we use the MCP inspector tool. From the root of this repository, run:
-
-```shell
-npm run inspect
-```
-
-This is equivalent to:
-
-```shell
-npx @modelcontextprotocol/inspector -- node dist/index.js
-```
-
-## Pull Request Guidelines
-
-1. Update documentation if necessary
-2. Ensure your PR includes only relevant changes
-3. Link any related issues in your PR description
-4. Keep PRs focused on a single topic
-
-## Code Standards
-
-- Use TypeScript for all new code
-- Follow the existing code style (indentation, naming conventions, etc.)
-- Comment your code when necessary, especially for complex logic
-- Use meaningful variable and function names
-
-## Reporting Issues
-
-When reporting issues, please include:
-
-- A clear description of the problem
-- Steps to reproduce
-- Expected vs. actual behavior
-- Version information
-- Environment details
-
-## Adding New Tools
-
-When adding new tools to the MCP server:
-
-1. Follow the existing pattern in `server.ts`
-2. Define clear parameter schemas using Zod
-3. Implement thorough error handling
-4. Add proper documentation for the tool
-5. Include examples of how to use the tool
-
-## Release Process
-
-Our release process is automated using GitHub Actions workflows:
-
-### Version Bumping
-
-1. To create a new version, go to the GitHub repository Actions tab
-2. Select the "Version Bump" workflow
-3. Click "Run workflow" and choose one of the following options:
-   - `patch` (e.g., 1.0.0 → 1.0.1) for backward-compatible bug fixes
-   - `minor` (e.g., 1.0.0 → 1.1.0) for backward-compatible new features
-   - `major` (e.g., 1.0.0 → 2.0.0) for breaking changes
-   - A specific version number (e.g., `1.2.3`)
-4. This creates a pull request with the version change
-5. Once approved and merged, the version is updated
-
-### Automatic Publishing
-
-When a version bump is merged to the main branch:
-
-1. The "Publish" workflow automatically runs
-2. It checks if the version already exists as a git tag
-3. If the version is new, it:
-   - Builds the package
-   - Publishes to NPM
-   - Creates a git tag for the version
-   - Creates a GitHub release with auto-generated release notes
-
-### Code Quality
-
-All pull requests automatically run through the "Code Health" workflow, which:
-
-- Verifies code style and formatting
-- Runs tests on multiple platforms (Ubuntu, macOS, Windows)
-
-## License
-
-By contributing to this project, you agree that your contributions will be licensed under the project's license.
-
-## Questions?
-
-If you have any questions or need help, please open an issue or reach out to the maintainers.

package/Dockerfile

@@ -1,11 +0,0 @@
-FROM node:22-alpine
-ARG VERSION=latest
-RUN addgroup -S mcp && adduser -S mcp -G mcp
-RUN npm install -g mongodb-mcp-server@${VERSION}
-USER mcp
-WORKDIR /home/mcp
-ENV MDB_MCP_LOGGERS=stderr,mcp
-ENTRYPOINT ["mongodb-mcp-server"]
-LABEL maintainer="MongoDB Inc <info@mongodb.com>"
-LABEL description="MongoDB MCP Server"
-LABEL version=${VERSION}

package/dist/common/atlas/accessListUtils.js

@@ -1,36 +0,0 @@
-import logger, { LogId } from "../logger.js";
-import { ApiClientError } from "./apiClientError.js";
-export const DEFAULT_ACCESS_LIST_COMMENT = "Added by MongoDB MCP Server to enable tool access";
-export async function makeCurrentIpAccessListEntry(apiClient, projectId, comment = DEFAULT_ACCESS_LIST_COMMENT) {
-    const { currentIpv4Address } = await apiClient.getIpInfo();
-    return {
-        groupId: projectId,
-        ipAddress: currentIpv4Address,
-        comment,
-    };
-}
-/**
- * Ensures the current public IP is in the access list for the given Atlas project.
- * If the IP is already present, this is a no-op.
- * @param apiClient The Atlas API client instance
- * @param projectId The Atlas project ID
- */
-export async function ensureCurrentIpInAccessList(apiClient, projectId) {
-    const entry = await makeCurrentIpAccessListEntry(apiClient, projectId, DEFAULT_ACCESS_LIST_COMMENT);
-    try {
-        await apiClient.createProjectIpAccessList({
-            params: { path: { groupId: projectId } },
-            body: [entry],
-        });
-        logger.debug(LogId.atlasIpAccessListAdded, "accessListUtils", `IP access list created: ${JSON.stringify(entry)}`);
-    }
-    catch (err) {
-        if (err instanceof ApiClientError && err.response?.status === 409) {
-            // 409 Conflict: entry already exists, log info
-            logger.debug(LogId.atlasIpAccessListAdded, "accessListUtils", `IP address ${entry.ipAddress} is already present in the access list for project ${projectId}.`);
-            return;
-        }
-        logger.warning(LogId.atlasIpAccessListAddFailure, "accessListUtils", `Error adding IP access list: ${err instanceof Error ? err.message : String(err)}`);
-    }
-}
-//# sourceMappingURL=accessListUtils.js.map

package/dist/common/atlas/accessListUtils.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"accessListUtils.js","sourceRoot":"","sources":["../../../src/common/atlas/accessListUtils.ts"],"names":[],"mappings":"AACA,OAAO,MAAM,EAAE,EAAE,KAAK,EAAE,MAAM,cAAc,CAAC;AAC7C,OAAO,EAAE,cAAc,EAAE,MAAM,qBAAqB,CAAC;AAErD,MAAM,CAAC,MAAM,2BAA2B,GAAG,mDAAmD,CAAC;AAE/F,MAAM,CAAC,KAAK,UAAU,4BAA4B,CAC9C,SAAoB,EACpB,SAAiB,EACjB,UAAkB,2BAA2B;IAE7C,MAAM,EAAE,kBAAkB,EAAE,GAAG,MAAM,SAAS,CAAC,SAAS,EAAE,CAAC;IAC3D,OAAO;QACH,OAAO,EAAE,SAAS;QAClB,SAAS,EAAE,kBAAkB;QAC7B,OAAO;KACV,CAAC;AACN,CAAC;AAED;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,2BAA2B,CAAC,SAAoB,EAAE,SAAiB;IACrF,MAAM,KAAK,GAAG,MAAM,4BAA4B,CAAC,SAAS,EAAE,SAAS,EAAE,2BAA2B,CAAC,CAAC;IACpG,IAAI,CAAC;QACD,MAAM,SAAS,CAAC,yBAAyB,CAAC;YACtC,MAAM,EAAE,EAAE,IAAI,EAAE,EAAE,OAAO,EAAE,SAAS,EAAE,EAAE;YACxC,IAAI,EAAE,CAAC,KAAK,CAAC;SAChB,CAAC,CAAC;QACH,MAAM,CAAC,KAAK,CACR,KAAK,CAAC,sBAAsB,EAC5B,iBAAiB,EACjB,2BAA2B,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,EAAE,CACrD,CAAC;IACN,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACX,IAAI,GAAG,YAAY,cAAc,IAAI,GAAG,CAAC,QAAQ,EAAE,MAAM,KAAK,GAAG,EAAE,CAAC;YAChE,+CAA+C;YAC/C,MAAM,CAAC,KAAK,CACR,KAAK,CAAC,sBAAsB,EAC5B,iBAAiB,EACjB,cAAc,KAAK,CAAC,SAAS,sDAAsD,SAAS,GAAG,CAClG,CAAC;YACF,OAAO;QACX,CAAC;QACD,MAAM,CAAC,OAAO,CACV,KAAK,CAAC,2BAA2B,EACjC,iBAAiB,EACjB,gCAAgC,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,EAAE,CACrF,CAAC;IACN,CAAC;AACL,CAAC"}