@strapi/upload 5.52.3 → 5.54.0

package/dist/server/mcp/register-upload-mcp-tools.js

@@ -0,0 +1,235 @@
+'use strict';
+
+var constants = require('../constants.js');
+var inputSchemas = require('./schemas/input-schemas.js');
+var outputSchemas = require('./schemas/output-schemas.js');
+var readHandlers = require('./handlers/read-handlers.js');
+var writeHandlers = require('./handlers/write-handlers.js');
+var folderHandlers = require('./handlers/folder-handlers.js');
+
+/**
+ * The Media Library MCP tools.
+ *
+ * Folder writes inherit the same `plugin::upload.assets.update` action rather than introducing a
+ * folder-specific one, matching what the admin UI enforces today. MCP-specific folder RBAC is
+ * out of scope.
+ *
+ * Renaming and moving are separate tools for both objects — rename/update changes attributes,
+ * move changes location — so an agent selects by intent instead of assembling a combined patch.
+ *
+ * The asset and folder tools stay separate for both move and delete, even though
+ * `/actions/bulk-move` accepts both id lists at once and `/actions/bulk-delete` accepts `fileIds`
+ * and `folderIds` together. Asset ids and folder ids are indistinguishable integers from separate
+ * namespaces, and both `media_list_assets` and `media_list_folders` return a plain `id`, so a
+ * combined tool would let an agent pass folder ids where assets were meant with nothing to
+ * object. On the delete side that mistake is unrecoverable, and two tools also let each
+ * description carry the warning matched to its own blast radius.
+ */ const buildUploadMcpToolDefinitions = ()=>[
+        {
+            name: 'media_list_assets',
+            title: 'Media: list assets',
+            description: 'List Media Library assets with pagination, folder / mime type / name filters and sorting. Assets are identified by a numeric id — media files are not documents and have no documentId.',
+            telemetry: {
+                source: 'upload',
+                name: 'list'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.read
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaListAssetsInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaListAssetsOutputSchema,
+            createHandler: readHandlers.createMediaListAssetsHandler
+        },
+        {
+            name: 'media_get_asset',
+            title: 'Media: get asset',
+            description: 'Get a single Media Library asset by its numeric id. Media files are not documents: use the numeric id, not a documentId.',
+            telemetry: {
+                source: 'upload',
+                name: 'get'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.read
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaGetAssetInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaGetAssetOutputSchema,
+            createHandler: readHandlers.createMediaGetAssetHandler
+        },
+        {
+            name: 'media_list_folders',
+            title: 'Media: list folders',
+            description: 'List the Media Library folder structure as a nested tree. Folders are identified by a numeric id; pass one as `folderId` to media_list_assets to list its contents.',
+            telemetry: {
+                source: 'upload',
+                name: 'list_folders'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.read
+                    }
+                ]
+            },
+            resolveOutputSchema: ()=>outputSchemas.mediaListFoldersOutputSchema,
+            createHandler: readHandlers.createMediaListFoldersHandler
+        },
+        {
+            name: 'media_update_asset',
+            title: 'Media: update asset metadata',
+            description: "Update the editable metadata of a Media Library asset, identified by its numeric id. Only name, alternativeText and caption can be written: use media_move_assets to change an asset's folder, and note that url, mime, size and the file contents are owned by the upload provider and cannot be edited over MCP.",
+            telemetry: {
+                source: 'upload',
+                name: 'update'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaUpdateAssetInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaUpdateAssetOutputSchema,
+            createHandler: writeHandlers.createMediaUpdateAssetHandler
+        },
+        {
+            name: 'media_move_assets',
+            title: 'Media: move assets between folders',
+            description: "Move Media Library assets into a different folder, in bulk. Takes `ids` — an array of numeric ASSET ids — and `folder`, the numeric id of the destination; pass `folder: null` to move them to the media library root. Both are required: use an array of one to move a single asset, and say null explicitly for the root.\n\nTakes ASSET ids only. Media files are not documents: use numeric ids, not documentIds.\n\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will move whichever unrelated asset happens to share that number, reporting that move as a success, while leaving the folder exactly where it was. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_move_folder to move a folder (which carries its whole subtree).\n\nMoving changes the folder only. Names, alt text, captions and the assets' public URLs are unaffected, so nothing referencing them breaks — use media_update_asset to edit metadata.\n\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the valid moves back. The response always reports `moved` (the assets that were moved) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`, and treat `moved` as done. This holds even when nothing moved at all: `moved` is then empty and every id is in `failed`. The one error that rejects the whole call is a destination folder that does not exist, which is checked before anything is moved.",
+            telemetry: {
+                source: 'upload',
+                name: 'move'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaMoveAssetsInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaMoveAssetsOutputSchema,
+            createHandler: writeHandlers.createMediaMoveAssetsHandler
+        },
+        {
+            name: 'media_delete_assets',
+            title: 'Media: delete assets (destructive)',
+            description: 'DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes Media Library assets by numeric id, in bulk — from the database AND from the storage provider, along with every generated thumbnail and size variant. There is no undo, no trash and no recycle bin. The deleted files stop being served immediately, so any live entry, page or export still referencing one will break.\n\nWHETHER AN ASSET IS USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose "used in" information over this API, so this tool cannot tell you whether an asset is referenced by any entry, and a successful delete is NOT evidence that nothing was using it. Confirm with the user before deleting.\n\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response lists exactly which assets WOULD be removed, and how many. Report those to the user, and only then call it again with `dryRun: false` to actually delete.\n\nTakes `ids`, an array of numeric ASSET ids — use an array of one to delete a single asset. Media files are not documents: use numeric ids, not documentIds.\n\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will silently delete whichever unrelated asset happens to share that number, while leaving the folder untouched. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_delete_folder to delete a folder. If you are not certain an id came from media_list_assets, run the dry run and check the returned name and folder before deleting.\n\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the completed deletions back, and those cannot be undone. The response always reports `deleted` (the assets removed, described in full because they can no longer be read back) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`. This holds on the dry run too, which reports the same split before anything is destroyed.',
+            telemetry: {
+                source: 'upload',
+                name: 'delete'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaDeleteAssetsInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaDeleteAssetsOutputSchema,
+            createHandler: writeHandlers.createMediaDeleteAssetsHandler
+        },
+        {
+            name: 'media_create_folder',
+            title: 'Media: create folder',
+            description: 'Create a Media Library folder, optionally inside an existing one. Folders are identified by a numeric id: pass `parent` to nest the new folder, or omit it to create the folder at the media library root. The name must be unique among its siblings and cannot contain slashes.',
+            telemetry: {
+                source: 'upload',
+                name: 'create_folder'
+            },
+            // `create`, not `update`, to match `POST /upload/folders` — the admin route for the same
+            // operation gates on `assets.create`. The other folder tools use `update` because their
+            // admin counterparts (`PUT /folders/:id` and both bulk actions) do.
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.create
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaCreateFolderInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaCreateFolderOutputSchema,
+            createHandler: folderHandlers.createMediaCreateFolderHandler
+        },
+        {
+            name: 'media_rename_folder',
+            title: 'Media: rename folder',
+            description: "Rename a Media Library folder, identified by its numeric id. Changes the folder name only and leaves its location, its contents and their URLs untouched — use media_move_folder to change which folder it sits in. The new name must be unique among the folder's siblings.",
+            telemetry: {
+                source: 'upload',
+                name: 'rename_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaRenameFolderInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaRenameFolderOutputSchema,
+            createHandler: folderHandlers.createMediaRenameFolderHandler
+        },
+        {
+            name: 'media_move_folder',
+            title: 'Media: move folder',
+            description: 'Move a Media Library folder into a different parent folder, identified by numeric ids. The folder keeps its name and carries all of its subfolders and files with it; pass `parent: null` to move it to the media library root. A folder cannot be moved into itself or into one of its own descendants. Use media_rename_folder to change the name instead.',
+            telemetry: {
+                source: 'upload',
+                name: 'move_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaMoveFolderInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaMoveFolderOutputSchema,
+            createHandler: folderHandlers.createMediaMoveFolderHandler
+        },
+        {
+            name: 'media_delete_folder',
+            title: 'Media: delete folder (destructive)',
+            description: 'DESTRUCTIVE AND IRREVERSIBLE. Deletes Media Library folders by numeric id and CASCADES: every subfolder and every file inside them is permanently deleted from the database and from the storage provider. There is no undo, no trash and no recycle bin, and the deleted files stop being served — any live entry or page still referencing one will break.\n\nWHETHER THE CONTAINED ASSETS ARE USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose "used in" information over this API, so this tool cannot tell you whether a file is referenced by an entry. Confirm with the user before deleting.\n\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response reports how many folders and files WOULD be removed. Only after reporting those counts should you call it again with `dryRun: false` to actually delete. Takes FOLDER ids only — asset ids are a separate namespace of integers; use media_delete_assets for individual assets. All or nothing: if ANY id does not resolve to a folder the whole call is rejected and nothing is deleted, so a list mixing folder and asset ids never deletes half of what it names.',
+            telemetry: {
+                source: 'upload',
+                name: 'delete_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: constants.ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>inputSchemas.mediaDeleteFolderInputSchema,
+            resolveOutputSchema: ()=>outputSchemas.mediaDeleteFolderOutputSchema,
+            createHandler: folderHandlers.createMediaDeleteFolderHandler
+        }
+    ];
+/**
+ * Registers the Media Library MCP tools via `strapi.ai.mcp.registerTool()`.
+ * Must be called from the plugin register phase, before the MCP HTTP server starts.
+ */ const registerUploadMcpTools = ({ strapi })=>{
+    // No `isEnabled()` gate: registerTool() only stores the definition, and the MCP server never
+    // exposes it when disabled, so registering unconditionally is a no-op there. The three
+    // definitions are static, so there is no derivation cost worth guarding either.
+    for (const tool of buildUploadMcpToolDefinitions()){
+        strapi.ai?.mcp?.registerTool(tool);
+    }
+};
+
+exports.buildUploadMcpToolDefinitions = buildUploadMcpToolDefinitions;
+exports.registerUploadMcpTools = registerUploadMcpTools;
+//# sourceMappingURL=register-upload-mcp-tools.js.map

package/dist/server/mcp/register-upload-mcp-tools.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-upload-mcp-tools.js","sources":["../../../server/src/mcp/register-upload-mcp-tools.ts"],"sourcesContent":["import type { Core } from '@strapi/types';\n\nimport { ACTIONS } from '../constants';\nimport type { UploadMcpTool } from './types';\nimport {\n  mediaListAssetsInputSchema,\n  mediaGetAssetInputSchema,\n  mediaListAssetsOutputSchema,\n  mediaGetAssetOutputSchema,\n  mediaListFoldersOutputSchema,\n  mediaUpdateAssetInputSchema,\n  mediaUpdateAssetOutputSchema,\n  mediaCreateFolderInputSchema,\n  mediaCreateFolderOutputSchema,\n  mediaRenameFolderInputSchema,\n  mediaRenameFolderOutputSchema,\n  mediaMoveFolderInputSchema,\n  mediaMoveFolderOutputSchema,\n  mediaDeleteFolderInputSchema,\n  mediaDeleteFolderOutputSchema,\n  mediaMoveAssetsInputSchema,\n  mediaMoveAssetsOutputSchema,\n  mediaDeleteAssetsInputSchema,\n  mediaDeleteAssetsOutputSchema,\n} from './schemas';\nimport {\n  createMediaListAssetsHandler,\n  createMediaGetAssetHandler,\n  createMediaListFoldersHandler,\n  createMediaUpdateAssetHandler,\n  createMediaCreateFolderHandler,\n  createMediaRenameFolderHandler,\n  createMediaMoveFolderHandler,\n  createMediaDeleteFolderHandler,\n  createMediaMoveAssetsHandler,\n  createMediaDeleteAssetsHandler,\n} from './handlers';\n\n/**\n * The Media Library MCP tools.\n *\n * Folder writes inherit the same `plugin::upload.assets.update` action rather than introducing a\n * folder-specific one, matching what the admin UI enforces today. MCP-specific folder RBAC is\n * out of scope.\n *\n * Renaming and moving are separate tools for both objects — rename/update changes attributes,\n * move changes location — so an agent selects by intent instead of assembling a combined patch.\n *\n * The asset and folder tools stay separate for both move and delete, even though\n * `/actions/bulk-move` accepts both id lists at once and `/actions/bulk-delete` accepts `fileIds`\n * and `folderIds` together. Asset ids and folder ids are indistinguishable integers from separate\n * namespaces, and both `media_list_assets` and `media_list_folders` return a plain `id`, so a\n * combined tool would let an agent pass folder ids where assets were meant with nothing to\n * object. On the delete side that mistake is unrecoverable, and two tools also let each\n * description carry the warning matched to its own blast radius.\n */\nexport const buildUploadMcpToolDefinitions = (): UploadMcpTool[] => [\n  {\n    name: 'media_list_assets',\n    title: 'Media: list assets',\n    description:\n      'List Media Library assets with pagination, folder / mime type / name filters and sorting. Assets are identified by a numeric id — media files are not documents and have no documentId.',\n    telemetry: { source: 'upload', name: 'list' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveInputSchema: () => mediaListAssetsInputSchema,\n    resolveOutputSchema: () => mediaListAssetsOutputSchema,\n    createHandler: createMediaListAssetsHandler,\n  },\n  {\n    name: 'media_get_asset',\n    title: 'Media: get asset',\n    description:\n      'Get a single Media Library asset by its numeric id. Media files are not documents: use the numeric id, not a documentId.',\n    telemetry: { source: 'upload', name: 'get' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveInputSchema: () => mediaGetAssetInputSchema,\n    resolveOutputSchema: () => mediaGetAssetOutputSchema,\n    createHandler: createMediaGetAssetHandler,\n  },\n  {\n    name: 'media_list_folders',\n    title: 'Media: list folders',\n    description:\n      'List the Media Library folder structure as a nested tree. Folders are identified by a numeric id; pass one as `folderId` to media_list_assets to list its contents.',\n    telemetry: { source: 'upload', name: 'list_folders' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveOutputSchema: () => mediaListFoldersOutputSchema,\n    createHandler: createMediaListFoldersHandler,\n  },\n  {\n    name: 'media_update_asset',\n    title: 'Media: update asset metadata',\n    description:\n      \"Update the editable metadata of a Media Library asset, identified by its numeric id. Only name, alternativeText and caption can be written: use media_move_assets to change an asset's folder, and note that url, mime, size and the file contents are owned by the upload provider and cannot be edited over MCP.\",\n    telemetry: { source: 'upload', name: 'update' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaUpdateAssetInputSchema,\n    resolveOutputSchema: () => mediaUpdateAssetOutputSchema,\n    createHandler: createMediaUpdateAssetHandler,\n  },\n  {\n    name: 'media_move_assets',\n    title: 'Media: move assets between folders',\n    description:\n      \"Move Media Library assets into a different folder, in bulk. Takes `ids` — an array of numeric ASSET ids — and `folder`, the numeric id of the destination; pass `folder: null` to move them to the media library root. Both are required: use an array of one to move a single asset, and say null explicitly for the root.\\n\\nTakes ASSET ids only. Media files are not documents: use numeric ids, not documentIds.\\n\\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will move whichever unrelated asset happens to share that number, reporting that move as a success, while leaving the folder exactly where it was. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_move_folder to move a folder (which carries its whole subtree).\\n\\nMoving changes the folder only. Names, alt text, captions and the assets' public URLs are unaffected, so nothing referencing them breaks — use media_update_asset to edit metadata.\\n\\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the valid moves back. The response always reports `moved` (the assets that were moved) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`, and treat `moved` as done. This holds even when nothing moved at all: `moved` is then empty and every id is in `failed`. The one error that rejects the whole call is a destination folder that does not exist, which is checked before anything is moved.\",\n    telemetry: { source: 'upload', name: 'move' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaMoveAssetsInputSchema,\n    resolveOutputSchema: () => mediaMoveAssetsOutputSchema,\n    createHandler: createMediaMoveAssetsHandler,\n  },\n  {\n    name: 'media_delete_assets',\n    title: 'Media: delete assets (destructive)',\n    description:\n      'DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes Media Library assets by numeric id, in bulk — from the database AND from the storage provider, along with every generated thumbnail and size variant. There is no undo, no trash and no recycle bin. The deleted files stop being served immediately, so any live entry, page or export still referencing one will break.\\n\\nWHETHER AN ASSET IS USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose \"used in\" information over this API, so this tool cannot tell you whether an asset is referenced by any entry, and a successful delete is NOT evidence that nothing was using it. Confirm with the user before deleting.\\n\\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response lists exactly which assets WOULD be removed, and how many. Report those to the user, and only then call it again with `dryRun: false` to actually delete.\\n\\nTakes `ids`, an array of numeric ASSET ids — use an array of one to delete a single asset. Media files are not documents: use numeric ids, not documentIds.\\n\\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will silently delete whichever unrelated asset happens to share that number, while leaving the folder untouched. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_delete_folder to delete a folder. If you are not certain an id came from media_list_assets, run the dry run and check the returned name and folder before deleting.\\n\\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the completed deletions back, and those cannot be undone. The response always reports `deleted` (the assets removed, described in full because they can no longer be read back) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`. This holds on the dry run too, which reports the same split before anything is destroyed.',\n    telemetry: { source: 'upload', name: 'delete' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaDeleteAssetsInputSchema,\n    resolveOutputSchema: () => mediaDeleteAssetsOutputSchema,\n    createHandler: createMediaDeleteAssetsHandler,\n  },\n  {\n    name: 'media_create_folder',\n    title: 'Media: create folder',\n    description:\n      'Create a Media Library folder, optionally inside an existing one. Folders are identified by a numeric id: pass `parent` to nest the new folder, or omit it to create the folder at the media library root. The name must be unique among its siblings and cannot contain slashes.',\n    telemetry: { source: 'upload', name: 'create_folder' },\n    // `create`, not `update`, to match `POST /upload/folders` — the admin route for the same\n    // operation gates on `assets.create`. The other folder tools use `update` because their\n    // admin counterparts (`PUT /folders/:id` and both bulk actions) do.\n    auth: { policies: [{ action: ACTIONS.create }] },\n    resolveInputSchema: () => mediaCreateFolderInputSchema,\n    resolveOutputSchema: () => mediaCreateFolderOutputSchema,\n    createHandler: createMediaCreateFolderHandler,\n  },\n  {\n    name: 'media_rename_folder',\n    title: 'Media: rename folder',\n    description:\n      \"Rename a Media Library folder, identified by its numeric id. Changes the folder name only and leaves its location, its contents and their URLs untouched — use media_move_folder to change which folder it sits in. The new name must be unique among the folder's siblings.\",\n    telemetry: { source: 'upload', name: 'rename_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaRenameFolderInputSchema,\n    resolveOutputSchema: () => mediaRenameFolderOutputSchema,\n    createHandler: createMediaRenameFolderHandler,\n  },\n  {\n    name: 'media_move_folder',\n    title: 'Media: move folder',\n    description:\n      'Move a Media Library folder into a different parent folder, identified by numeric ids. The folder keeps its name and carries all of its subfolders and files with it; pass `parent: null` to move it to the media library root. A folder cannot be moved into itself or into one of its own descendants. Use media_rename_folder to change the name instead.',\n    telemetry: { source: 'upload', name: 'move_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaMoveFolderInputSchema,\n    resolveOutputSchema: () => mediaMoveFolderOutputSchema,\n    createHandler: createMediaMoveFolderHandler,\n  },\n  {\n    name: 'media_delete_folder',\n    title: 'Media: delete folder (destructive)',\n    description:\n      'DESTRUCTIVE AND IRREVERSIBLE. Deletes Media Library folders by numeric id and CASCADES: every subfolder and every file inside them is permanently deleted from the database and from the storage provider. There is no undo, no trash and no recycle bin, and the deleted files stop being served — any live entry or page still referencing one will break.\\n\\nWHETHER THE CONTAINED ASSETS ARE USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose \"used in\" information over this API, so this tool cannot tell you whether a file is referenced by an entry. Confirm with the user before deleting.\\n\\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response reports how many folders and files WOULD be removed. Only after reporting those counts should you call it again with `dryRun: false` to actually delete. Takes FOLDER ids only — asset ids are a separate namespace of integers; use media_delete_assets for individual assets. All or nothing: if ANY id does not resolve to a folder the whole call is rejected and nothing is deleted, so a list mixing folder and asset ids never deletes half of what it names.',\n    telemetry: { source: 'upload', name: 'delete_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaDeleteFolderInputSchema,\n    resolveOutputSchema: () => mediaDeleteFolderOutputSchema,\n    createHandler: createMediaDeleteFolderHandler,\n  },\n];\n\n/**\n * Registers the Media Library MCP tools via `strapi.ai.mcp.registerTool()`.\n * Must be called from the plugin register phase, before the MCP HTTP server starts.\n */\nexport const registerUploadMcpTools = ({ strapi }: { strapi: Core.Strapi }): void => {\n  // No `isEnabled()` gate: registerTool() only stores the definition, and the MCP server never\n  // exposes it when disabled, so registering unconditionally is a no-op there. The three\n  // definitions are static, so there is no derivation cost worth guarding either.\n  for (const tool of buildUploadMcpToolDefinitions()) {\n    strapi.ai?.mcp?.registerTool(tool);\n  }\n};\n"],"names":["buildUploadMcpToolDefinitions","name","title","description","telemetry","source","auth","policies","action","ACTIONS","read","resolveInputSchema","mediaListAssetsInputSchema","resolveOutputSchema","mediaListAssetsOutputSchema","createHandler","createMediaListAssetsHandler","mediaGetAssetInputSchema","mediaGetAssetOutputSchema","createMediaGetAssetHandler","mediaListFoldersOutputSchema","createMediaListFoldersHandler","update","mediaUpdateAssetInputSchema","mediaUpdateAssetOutputSchema","createMediaUpdateAssetHandler","mediaMoveAssetsInputSchema","mediaMoveAssetsOutputSchema","createMediaMoveAssetsHandler","mediaDeleteAssetsInputSchema","mediaDeleteAssetsOutputSchema","createMediaDeleteAssetsHandler","create","mediaCreateFolderInputSchema","mediaCreateFolderOutputSchema","createMediaCreateFolderHandler","mediaRenameFolderInputSchema","mediaRenameFolderOutputSchema","createMediaRenameFolderHandler","mediaMoveFolderInputSchema","mediaMoveFolderOutputSchema","createMediaMoveFolderHandler","mediaDeleteFolderInputSchema","mediaDeleteFolderOutputSchema","createMediaDeleteFolderHandler","registerUploadMcpTools","strapi","tool","ai","mcp","registerTool"],"mappings":";;;;;;;;;AAsCA;;;;;;;;;;;;;;;;;IAkBO,MAAMA,6BAAAA,GAAgC,IAAuB;AAClE,QAAA;YACEC,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oBAAA;YACPC,WAAAA,EACE,yLAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAO,aAAA;YAC5CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CC,YAAAA,kBAAAA,EAAoB,IAAMC,uCAAAA;AAC1BC,YAAAA,mBAAAA,EAAqB,IAAMC,yCAAAA;YAC3BC,aAAAA,EAAeC;AACjB,SAAA;AACA,QAAA;YACEf,IAAAA,EAAM,iBAAA;YACNC,KAAAA,EAAO,kBAAA;YACPC,WAAAA,EACE,0HAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAM,aAAA;YAC3CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CC,YAAAA,kBAAAA,EAAoB,IAAMM,qCAAAA;AAC1BJ,YAAAA,mBAAAA,EAAqB,IAAMK,uCAAAA;YAC3BH,aAAAA,EAAeI;AACjB,SAAA;AACA,QAAA;YACElB,IAAAA,EAAM,oBAAA;YACNC,KAAAA,EAAO,qBAAA;YACPC,WAAAA,EACE,qKAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAe,aAAA;YACpDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CG,YAAAA,mBAAAA,EAAqB,IAAMO,0CAAAA;YAC3BL,aAAAA,EAAeM;AACjB,SAAA;AACA,QAAA;YACEpB,IAAAA,EAAM,oBAAA;YACNC,KAAAA,EAAO,8BAAA;YACPC,WAAAA,EACE,oTAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAS,aAAA;YAC9CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMY,wCAAAA;AAC1BV,YAAAA,mBAAAA,EAAqB,IAAMW,0CAAAA;YAC3BT,aAAAA,EAAeU;AACjB,SAAA;AACA,QAAA;YACExB,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,+yDAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAO,aAAA;YAC5CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMe,uCAAAA;AAC1Bb,YAAAA,mBAAAA,EAAqB,IAAMc,yCAAAA;YAC3BZ,aAAAA,EAAea;AACjB,SAAA;AACA,QAAA;YACE3B,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,gyEAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAS,aAAA;YAC9CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMkB,yCAAAA;AAC1BhB,YAAAA,mBAAAA,EAAqB,IAAMiB,2CAAAA;YAC3Bf,aAAAA,EAAegB;AACjB,SAAA;AACA,QAAA;YACE9B,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,sBAAA;YACPC,WAAAA,EACE,mRAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;;;;YAIrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQuB;AAAO;AAAE;AAAC,aAAA;AAC/CrB,YAAAA,kBAAAA,EAAoB,IAAMsB,yCAAAA;AAC1BpB,YAAAA,mBAAAA,EAAqB,IAAMqB,2CAAAA;YAC3BnB,aAAAA,EAAeoB;AACjB,SAAA;AACA,QAAA;YACElC,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,sBAAA;YACPC,WAAAA,EACE,8QAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;YACrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMyB,yCAAAA;AAC1BvB,YAAAA,mBAAAA,EAAqB,IAAMwB,2CAAAA;YAC3BtB,aAAAA,EAAeuB;AACjB,SAAA;AACA,QAAA;YACErC,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oBAAA;YACPC,WAAAA,EACE,8VAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAc,aAAA;YACnDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAM4B,uCAAAA;AAC1B1B,YAAAA,mBAAAA,EAAqB,IAAM2B,yCAAAA;YAC3BzB,aAAAA,EAAe0B;AACjB,SAAA;AACA,QAAA;YACExC,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,yoCAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;YACrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,kBAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAM+B,yCAAAA;AAC1B7B,YAAAA,mBAAAA,EAAqB,IAAM8B,2CAAAA;YAC3B5B,aAAAA,EAAe6B;AACjB;;AAGF;;;AAGC,IACM,MAAMC,sBAAAA,GAAyB,CAAC,EAAEC,MAAM,EAA2B,GAAA;;;;IAIxE,KAAK,MAAMC,QAAQ/C,6BAAAA,EAAAA,CAAiC;QAClD8C,MAAAA,CAAOE,EAAE,EAAEC,GAAAA,EAAKC,YAAAA,CAAaH,IAAAA,CAAAA;AAC/B,IAAA;AACF;;;;;"}

package/dist/server/mcp/register-upload-mcp-tools.mjs

@@ -0,0 +1,232 @@
+import { ACTIONS } from '../constants.mjs';
+import { mediaListAssetsInputSchema, mediaGetAssetInputSchema, mediaUpdateAssetInputSchema, mediaMoveAssetsInputSchema, mediaDeleteAssetsInputSchema, mediaCreateFolderInputSchema, mediaRenameFolderInputSchema, mediaMoveFolderInputSchema, mediaDeleteFolderInputSchema } from './schemas/input-schemas.mjs';
+import { mediaListAssetsOutputSchema, mediaGetAssetOutputSchema, mediaListFoldersOutputSchema, mediaUpdateAssetOutputSchema, mediaMoveAssetsOutputSchema, mediaDeleteAssetsOutputSchema, mediaCreateFolderOutputSchema, mediaRenameFolderOutputSchema, mediaMoveFolderOutputSchema, mediaDeleteFolderOutputSchema } from './schemas/output-schemas.mjs';
+import { createMediaListAssetsHandler, createMediaGetAssetHandler, createMediaListFoldersHandler } from './handlers/read-handlers.mjs';
+import { createMediaUpdateAssetHandler, createMediaMoveAssetsHandler, createMediaDeleteAssetsHandler } from './handlers/write-handlers.mjs';
+import { createMediaCreateFolderHandler, createMediaRenameFolderHandler, createMediaMoveFolderHandler, createMediaDeleteFolderHandler } from './handlers/folder-handlers.mjs';
+
+/**
+ * The Media Library MCP tools.
+ *
+ * Folder writes inherit the same `plugin::upload.assets.update` action rather than introducing a
+ * folder-specific one, matching what the admin UI enforces today. MCP-specific folder RBAC is
+ * out of scope.
+ *
+ * Renaming and moving are separate tools for both objects — rename/update changes attributes,
+ * move changes location — so an agent selects by intent instead of assembling a combined patch.
+ *
+ * The asset and folder tools stay separate for both move and delete, even though
+ * `/actions/bulk-move` accepts both id lists at once and `/actions/bulk-delete` accepts `fileIds`
+ * and `folderIds` together. Asset ids and folder ids are indistinguishable integers from separate
+ * namespaces, and both `media_list_assets` and `media_list_folders` return a plain `id`, so a
+ * combined tool would let an agent pass folder ids where assets were meant with nothing to
+ * object. On the delete side that mistake is unrecoverable, and two tools also let each
+ * description carry the warning matched to its own blast radius.
+ */ const buildUploadMcpToolDefinitions = ()=>[
+        {
+            name: 'media_list_assets',
+            title: 'Media: list assets',
+            description: 'List Media Library assets with pagination, folder / mime type / name filters and sorting. Assets are identified by a numeric id — media files are not documents and have no documentId.',
+            telemetry: {
+                source: 'upload',
+                name: 'list'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.read
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaListAssetsInputSchema,
+            resolveOutputSchema: ()=>mediaListAssetsOutputSchema,
+            createHandler: createMediaListAssetsHandler
+        },
+        {
+            name: 'media_get_asset',
+            title: 'Media: get asset',
+            description: 'Get a single Media Library asset by its numeric id. Media files are not documents: use the numeric id, not a documentId.',
+            telemetry: {
+                source: 'upload',
+                name: 'get'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.read
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaGetAssetInputSchema,
+            resolveOutputSchema: ()=>mediaGetAssetOutputSchema,
+            createHandler: createMediaGetAssetHandler
+        },
+        {
+            name: 'media_list_folders',
+            title: 'Media: list folders',
+            description: 'List the Media Library folder structure as a nested tree. Folders are identified by a numeric id; pass one as `folderId` to media_list_assets to list its contents.',
+            telemetry: {
+                source: 'upload',
+                name: 'list_folders'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.read
+                    }
+                ]
+            },
+            resolveOutputSchema: ()=>mediaListFoldersOutputSchema,
+            createHandler: createMediaListFoldersHandler
+        },
+        {
+            name: 'media_update_asset',
+            title: 'Media: update asset metadata',
+            description: "Update the editable metadata of a Media Library asset, identified by its numeric id. Only name, alternativeText and caption can be written: use media_move_assets to change an asset's folder, and note that url, mime, size and the file contents are owned by the upload provider and cannot be edited over MCP.",
+            telemetry: {
+                source: 'upload',
+                name: 'update'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaUpdateAssetInputSchema,
+            resolveOutputSchema: ()=>mediaUpdateAssetOutputSchema,
+            createHandler: createMediaUpdateAssetHandler
+        },
+        {
+            name: 'media_move_assets',
+            title: 'Media: move assets between folders',
+            description: "Move Media Library assets into a different folder, in bulk. Takes `ids` — an array of numeric ASSET ids — and `folder`, the numeric id of the destination; pass `folder: null` to move them to the media library root. Both are required: use an array of one to move a single asset, and say null explicitly for the root.\n\nTakes ASSET ids only. Media files are not documents: use numeric ids, not documentIds.\n\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will move whichever unrelated asset happens to share that number, reporting that move as a success, while leaving the folder exactly where it was. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_move_folder to move a folder (which carries its whole subtree).\n\nMoving changes the folder only. Names, alt text, captions and the assets' public URLs are unaffected, so nothing referencing them breaks — use media_update_asset to edit metadata.\n\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the valid moves back. The response always reports `moved` (the assets that were moved) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`, and treat `moved` as done. This holds even when nothing moved at all: `moved` is then empty and every id is in `failed`. The one error that rejects the whole call is a destination folder that does not exist, which is checked before anything is moved.",
+            telemetry: {
+                source: 'upload',
+                name: 'move'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaMoveAssetsInputSchema,
+            resolveOutputSchema: ()=>mediaMoveAssetsOutputSchema,
+            createHandler: createMediaMoveAssetsHandler
+        },
+        {
+            name: 'media_delete_assets',
+            title: 'Media: delete assets (destructive)',
+            description: 'DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes Media Library assets by numeric id, in bulk — from the database AND from the storage provider, along with every generated thumbnail and size variant. There is no undo, no trash and no recycle bin. The deleted files stop being served immediately, so any live entry, page or export still referencing one will break.\n\nWHETHER AN ASSET IS USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose "used in" information over this API, so this tool cannot tell you whether an asset is referenced by any entry, and a successful delete is NOT evidence that nothing was using it. Confirm with the user before deleting.\n\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response lists exactly which assets WOULD be removed, and how many. Report those to the user, and only then call it again with `dryRun: false` to actually delete.\n\nTakes `ids`, an array of numeric ASSET ids — use an array of one to delete a single asset. Media files are not documents: use numeric ids, not documentIds.\n\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will silently delete whichever unrelated asset happens to share that number, while leaving the folder untouched. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_delete_folder to delete a folder. If you are not certain an id came from media_list_assets, run the dry run and check the returned name and folder before deleting.\n\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the completed deletions back, and those cannot be undone. The response always reports `deleted` (the assets removed, described in full because they can no longer be read back) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`. This holds on the dry run too, which reports the same split before anything is destroyed.',
+            telemetry: {
+                source: 'upload',
+                name: 'delete'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaDeleteAssetsInputSchema,
+            resolveOutputSchema: ()=>mediaDeleteAssetsOutputSchema,
+            createHandler: createMediaDeleteAssetsHandler
+        },
+        {
+            name: 'media_create_folder',
+            title: 'Media: create folder',
+            description: 'Create a Media Library folder, optionally inside an existing one. Folders are identified by a numeric id: pass `parent` to nest the new folder, or omit it to create the folder at the media library root. The name must be unique among its siblings and cannot contain slashes.',
+            telemetry: {
+                source: 'upload',
+                name: 'create_folder'
+            },
+            // `create`, not `update`, to match `POST /upload/folders` — the admin route for the same
+            // operation gates on `assets.create`. The other folder tools use `update` because their
+            // admin counterparts (`PUT /folders/:id` and both bulk actions) do.
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.create
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaCreateFolderInputSchema,
+            resolveOutputSchema: ()=>mediaCreateFolderOutputSchema,
+            createHandler: createMediaCreateFolderHandler
+        },
+        {
+            name: 'media_rename_folder',
+            title: 'Media: rename folder',
+            description: "Rename a Media Library folder, identified by its numeric id. Changes the folder name only and leaves its location, its contents and their URLs untouched — use media_move_folder to change which folder it sits in. The new name must be unique among the folder's siblings.",
+            telemetry: {
+                source: 'upload',
+                name: 'rename_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaRenameFolderInputSchema,
+            resolveOutputSchema: ()=>mediaRenameFolderOutputSchema,
+            createHandler: createMediaRenameFolderHandler
+        },
+        {
+            name: 'media_move_folder',
+            title: 'Media: move folder',
+            description: 'Move a Media Library folder into a different parent folder, identified by numeric ids. The folder keeps its name and carries all of its subfolders and files with it; pass `parent: null` to move it to the media library root. A folder cannot be moved into itself or into one of its own descendants. Use media_rename_folder to change the name instead.',
+            telemetry: {
+                source: 'upload',
+                name: 'move_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaMoveFolderInputSchema,
+            resolveOutputSchema: ()=>mediaMoveFolderOutputSchema,
+            createHandler: createMediaMoveFolderHandler
+        },
+        {
+            name: 'media_delete_folder',
+            title: 'Media: delete folder (destructive)',
+            description: 'DESTRUCTIVE AND IRREVERSIBLE. Deletes Media Library folders by numeric id and CASCADES: every subfolder and every file inside them is permanently deleted from the database and from the storage provider. There is no undo, no trash and no recycle bin, and the deleted files stop being served — any live entry or page still referencing one will break.\n\nWHETHER THE CONTAINED ASSETS ARE USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose "used in" information over this API, so this tool cannot tell you whether a file is referenced by an entry. Confirm with the user before deleting.\n\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response reports how many folders and files WOULD be removed. Only after reporting those counts should you call it again with `dryRun: false` to actually delete. Takes FOLDER ids only — asset ids are a separate namespace of integers; use media_delete_assets for individual assets. All or nothing: if ANY id does not resolve to a folder the whole call is rejected and nothing is deleted, so a list mixing folder and asset ids never deletes half of what it names.',
+            telemetry: {
+                source: 'upload',
+                name: 'delete_folder'
+            },
+            auth: {
+                policies: [
+                    {
+                        action: ACTIONS.update
+                    }
+                ]
+            },
+            resolveInputSchema: ()=>mediaDeleteFolderInputSchema,
+            resolveOutputSchema: ()=>mediaDeleteFolderOutputSchema,
+            createHandler: createMediaDeleteFolderHandler
+        }
+    ];
+/**
+ * Registers the Media Library MCP tools via `strapi.ai.mcp.registerTool()`.
+ * Must be called from the plugin register phase, before the MCP HTTP server starts.
+ */ const registerUploadMcpTools = ({ strapi })=>{
+    // No `isEnabled()` gate: registerTool() only stores the definition, and the MCP server never
+    // exposes it when disabled, so registering unconditionally is a no-op there. The three
+    // definitions are static, so there is no derivation cost worth guarding either.
+    for (const tool of buildUploadMcpToolDefinitions()){
+        strapi.ai?.mcp?.registerTool(tool);
+    }
+};
+
+export { buildUploadMcpToolDefinitions, registerUploadMcpTools };
+//# sourceMappingURL=register-upload-mcp-tools.mjs.map

package/dist/server/mcp/register-upload-mcp-tools.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-upload-mcp-tools.mjs","sources":["../../../server/src/mcp/register-upload-mcp-tools.ts"],"sourcesContent":["import type { Core } from '@strapi/types';\n\nimport { ACTIONS } from '../constants';\nimport type { UploadMcpTool } from './types';\nimport {\n  mediaListAssetsInputSchema,\n  mediaGetAssetInputSchema,\n  mediaListAssetsOutputSchema,\n  mediaGetAssetOutputSchema,\n  mediaListFoldersOutputSchema,\n  mediaUpdateAssetInputSchema,\n  mediaUpdateAssetOutputSchema,\n  mediaCreateFolderInputSchema,\n  mediaCreateFolderOutputSchema,\n  mediaRenameFolderInputSchema,\n  mediaRenameFolderOutputSchema,\n  mediaMoveFolderInputSchema,\n  mediaMoveFolderOutputSchema,\n  mediaDeleteFolderInputSchema,\n  mediaDeleteFolderOutputSchema,\n  mediaMoveAssetsInputSchema,\n  mediaMoveAssetsOutputSchema,\n  mediaDeleteAssetsInputSchema,\n  mediaDeleteAssetsOutputSchema,\n} from './schemas';\nimport {\n  createMediaListAssetsHandler,\n  createMediaGetAssetHandler,\n  createMediaListFoldersHandler,\n  createMediaUpdateAssetHandler,\n  createMediaCreateFolderHandler,\n  createMediaRenameFolderHandler,\n  createMediaMoveFolderHandler,\n  createMediaDeleteFolderHandler,\n  createMediaMoveAssetsHandler,\n  createMediaDeleteAssetsHandler,\n} from './handlers';\n\n/**\n * The Media Library MCP tools.\n *\n * Folder writes inherit the same `plugin::upload.assets.update` action rather than introducing a\n * folder-specific one, matching what the admin UI enforces today. MCP-specific folder RBAC is\n * out of scope.\n *\n * Renaming and moving are separate tools for both objects — rename/update changes attributes,\n * move changes location — so an agent selects by intent instead of assembling a combined patch.\n *\n * The asset and folder tools stay separate for both move and delete, even though\n * `/actions/bulk-move` accepts both id lists at once and `/actions/bulk-delete` accepts `fileIds`\n * and `folderIds` together. Asset ids and folder ids are indistinguishable integers from separate\n * namespaces, and both `media_list_assets` and `media_list_folders` return a plain `id`, so a\n * combined tool would let an agent pass folder ids where assets were meant with nothing to\n * object. On the delete side that mistake is unrecoverable, and two tools also let each\n * description carry the warning matched to its own blast radius.\n */\nexport const buildUploadMcpToolDefinitions = (): UploadMcpTool[] => [\n  {\n    name: 'media_list_assets',\n    title: 'Media: list assets',\n    description:\n      'List Media Library assets with pagination, folder / mime type / name filters and sorting. Assets are identified by a numeric id — media files are not documents and have no documentId.',\n    telemetry: { source: 'upload', name: 'list' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveInputSchema: () => mediaListAssetsInputSchema,\n    resolveOutputSchema: () => mediaListAssetsOutputSchema,\n    createHandler: createMediaListAssetsHandler,\n  },\n  {\n    name: 'media_get_asset',\n    title: 'Media: get asset',\n    description:\n      'Get a single Media Library asset by its numeric id. Media files are not documents: use the numeric id, not a documentId.',\n    telemetry: { source: 'upload', name: 'get' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveInputSchema: () => mediaGetAssetInputSchema,\n    resolveOutputSchema: () => mediaGetAssetOutputSchema,\n    createHandler: createMediaGetAssetHandler,\n  },\n  {\n    name: 'media_list_folders',\n    title: 'Media: list folders',\n    description:\n      'List the Media Library folder structure as a nested tree. Folders are identified by a numeric id; pass one as `folderId` to media_list_assets to list its contents.',\n    telemetry: { source: 'upload', name: 'list_folders' },\n    auth: { policies: [{ action: ACTIONS.read }] },\n    resolveOutputSchema: () => mediaListFoldersOutputSchema,\n    createHandler: createMediaListFoldersHandler,\n  },\n  {\n    name: 'media_update_asset',\n    title: 'Media: update asset metadata',\n    description:\n      \"Update the editable metadata of a Media Library asset, identified by its numeric id. Only name, alternativeText and caption can be written: use media_move_assets to change an asset's folder, and note that url, mime, size and the file contents are owned by the upload provider and cannot be edited over MCP.\",\n    telemetry: { source: 'upload', name: 'update' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaUpdateAssetInputSchema,\n    resolveOutputSchema: () => mediaUpdateAssetOutputSchema,\n    createHandler: createMediaUpdateAssetHandler,\n  },\n  {\n    name: 'media_move_assets',\n    title: 'Media: move assets between folders',\n    description:\n      \"Move Media Library assets into a different folder, in bulk. Takes `ids` — an array of numeric ASSET ids — and `folder`, the numeric id of the destination; pass `folder: null` to move them to the media library root. Both are required: use an array of one to move a single asset, and say null explicitly for the root.\\n\\nTakes ASSET ids only. Media files are not documents: use numeric ids, not documentIds.\\n\\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will move whichever unrelated asset happens to share that number, reporting that move as a success, while leaving the folder exactly where it was. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_move_folder to move a folder (which carries its whole subtree).\\n\\nMoving changes the folder only. Names, alt text, captions and the assets' public URLs are unaffected, so nothing referencing them breaks — use media_update_asset to edit metadata.\\n\\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the valid moves back. The response always reports `moved` (the assets that were moved) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`, and treat `moved` as done. This holds even when nothing moved at all: `moved` is then empty and every id is in `failed`. The one error that rejects the whole call is a destination folder that does not exist, which is checked before anything is moved.\",\n    telemetry: { source: 'upload', name: 'move' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaMoveAssetsInputSchema,\n    resolveOutputSchema: () => mediaMoveAssetsOutputSchema,\n    createHandler: createMediaMoveAssetsHandler,\n  },\n  {\n    name: 'media_delete_assets',\n    title: 'Media: delete assets (destructive)',\n    description:\n      'DESTRUCTIVE AND IRREVERSIBLE. Permanently deletes Media Library assets by numeric id, in bulk — from the database AND from the storage provider, along with every generated thumbnail and size variant. There is no undo, no trash and no recycle bin. The deleted files stop being served immediately, so any live entry, page or export still referencing one will break.\\n\\nWHETHER AN ASSET IS USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose \"used in\" information over this API, so this tool cannot tell you whether an asset is referenced by any entry, and a successful delete is NOT evidence that nothing was using it. Confirm with the user before deleting.\\n\\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response lists exactly which assets WOULD be removed, and how many. Report those to the user, and only then call it again with `dryRun: false` to actually delete.\\n\\nTakes `ids`, an array of numeric ASSET ids — use an array of one to delete a single asset. Media files are not documents: use numeric ids, not documentIds.\\n\\nNEVER PASS A FOLDER ID. Asset ids and folder ids are separate, independently numbered namespaces, and the SAME NUMBER OFTEN NAMES BOTH an asset and a folder. This tool always reads the number as an ASSET id: hand it a folder id and it will silently delete whichever unrelated asset happens to share that number, while leaving the folder untouched. Nothing in the request can express which one you meant, so the server cannot catch this for you — only an id matching no asset at all is reported as failed. Take ids only from media_list_assets or media_get_asset, never from media_list_folders, and use media_delete_folder to delete a folder. If you are not certain an id came from media_list_assets, run the dry run and check the returned name and folder before deleting.\\n\\nPARTIAL SUCCESS IS POSSIBLE: a bad id among good ones does NOT roll the completed deletions back, and those cannot be undone. The response always reports `deleted` (the assets removed, described in full because they can no longer be read back) and `failed` (each remaining id with a reason), which together account for every id you passed — so retry only the ids in `failed`. This holds on the dry run too, which reports the same split before anything is destroyed.',\n    telemetry: { source: 'upload', name: 'delete' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaDeleteAssetsInputSchema,\n    resolveOutputSchema: () => mediaDeleteAssetsOutputSchema,\n    createHandler: createMediaDeleteAssetsHandler,\n  },\n  {\n    name: 'media_create_folder',\n    title: 'Media: create folder',\n    description:\n      'Create a Media Library folder, optionally inside an existing one. Folders are identified by a numeric id: pass `parent` to nest the new folder, or omit it to create the folder at the media library root. The name must be unique among its siblings and cannot contain slashes.',\n    telemetry: { source: 'upload', name: 'create_folder' },\n    // `create`, not `update`, to match `POST /upload/folders` — the admin route for the same\n    // operation gates on `assets.create`. The other folder tools use `update` because their\n    // admin counterparts (`PUT /folders/:id` and both bulk actions) do.\n    auth: { policies: [{ action: ACTIONS.create }] },\n    resolveInputSchema: () => mediaCreateFolderInputSchema,\n    resolveOutputSchema: () => mediaCreateFolderOutputSchema,\n    createHandler: createMediaCreateFolderHandler,\n  },\n  {\n    name: 'media_rename_folder',\n    title: 'Media: rename folder',\n    description:\n      \"Rename a Media Library folder, identified by its numeric id. Changes the folder name only and leaves its location, its contents and their URLs untouched — use media_move_folder to change which folder it sits in. The new name must be unique among the folder's siblings.\",\n    telemetry: { source: 'upload', name: 'rename_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaRenameFolderInputSchema,\n    resolveOutputSchema: () => mediaRenameFolderOutputSchema,\n    createHandler: createMediaRenameFolderHandler,\n  },\n  {\n    name: 'media_move_folder',\n    title: 'Media: move folder',\n    description:\n      'Move a Media Library folder into a different parent folder, identified by numeric ids. The folder keeps its name and carries all of its subfolders and files with it; pass `parent: null` to move it to the media library root. A folder cannot be moved into itself or into one of its own descendants. Use media_rename_folder to change the name instead.',\n    telemetry: { source: 'upload', name: 'move_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaMoveFolderInputSchema,\n    resolveOutputSchema: () => mediaMoveFolderOutputSchema,\n    createHandler: createMediaMoveFolderHandler,\n  },\n  {\n    name: 'media_delete_folder',\n    title: 'Media: delete folder (destructive)',\n    description:\n      'DESTRUCTIVE AND IRREVERSIBLE. Deletes Media Library folders by numeric id and CASCADES: every subfolder and every file inside them is permanently deleted from the database and from the storage provider. There is no undo, no trash and no recycle bin, and the deleted files stop being served — any live entry or page still referencing one will break.\\n\\nWHETHER THE CONTAINED ASSETS ARE USED IN PUBLISHED CONTENT CANNOT BE CHECKED: Strapi does not expose \"used in\" information over this API, so this tool cannot tell you whether a file is referenced by an entry. Confirm with the user before deleting.\\n\\nCall it first WITHOUT `dryRun` (or with `dryRun: true`) to preview: nothing is deleted and the response reports how many folders and files WOULD be removed. Only after reporting those counts should you call it again with `dryRun: false` to actually delete. Takes FOLDER ids only — asset ids are a separate namespace of integers; use media_delete_assets for individual assets. All or nothing: if ANY id does not resolve to a folder the whole call is rejected and nothing is deleted, so a list mixing folder and asset ids never deletes half of what it names.',\n    telemetry: { source: 'upload', name: 'delete_folder' },\n    auth: { policies: [{ action: ACTIONS.update }] },\n    resolveInputSchema: () => mediaDeleteFolderInputSchema,\n    resolveOutputSchema: () => mediaDeleteFolderOutputSchema,\n    createHandler: createMediaDeleteFolderHandler,\n  },\n];\n\n/**\n * Registers the Media Library MCP tools via `strapi.ai.mcp.registerTool()`.\n * Must be called from the plugin register phase, before the MCP HTTP server starts.\n */\nexport const registerUploadMcpTools = ({ strapi }: { strapi: Core.Strapi }): void => {\n  // No `isEnabled()` gate: registerTool() only stores the definition, and the MCP server never\n  // exposes it when disabled, so registering unconditionally is a no-op there. The three\n  // definitions are static, so there is no derivation cost worth guarding either.\n  for (const tool of buildUploadMcpToolDefinitions()) {\n    strapi.ai?.mcp?.registerTool(tool);\n  }\n};\n"],"names":["buildUploadMcpToolDefinitions","name","title","description","telemetry","source","auth","policies","action","ACTIONS","read","resolveInputSchema","mediaListAssetsInputSchema","resolveOutputSchema","mediaListAssetsOutputSchema","createHandler","createMediaListAssetsHandler","mediaGetAssetInputSchema","mediaGetAssetOutputSchema","createMediaGetAssetHandler","mediaListFoldersOutputSchema","createMediaListFoldersHandler","update","mediaUpdateAssetInputSchema","mediaUpdateAssetOutputSchema","createMediaUpdateAssetHandler","mediaMoveAssetsInputSchema","mediaMoveAssetsOutputSchema","createMediaMoveAssetsHandler","mediaDeleteAssetsInputSchema","mediaDeleteAssetsOutputSchema","createMediaDeleteAssetsHandler","create","mediaCreateFolderInputSchema","mediaCreateFolderOutputSchema","createMediaCreateFolderHandler","mediaRenameFolderInputSchema","mediaRenameFolderOutputSchema","createMediaRenameFolderHandler","mediaMoveFolderInputSchema","mediaMoveFolderOutputSchema","createMediaMoveFolderHandler","mediaDeleteFolderInputSchema","mediaDeleteFolderOutputSchema","createMediaDeleteFolderHandler","registerUploadMcpTools","strapi","tool","ai","mcp","registerTool"],"mappings":";;;;;;;AAsCA;;;;;;;;;;;;;;;;;IAkBO,MAAMA,6BAAAA,GAAgC,IAAuB;AAClE,QAAA;YACEC,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oBAAA;YACPC,WAAAA,EACE,yLAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAO,aAAA;YAC5CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CC,YAAAA,kBAAAA,EAAoB,IAAMC,0BAAAA;AAC1BC,YAAAA,mBAAAA,EAAqB,IAAMC,2BAAAA;YAC3BC,aAAAA,EAAeC;AACjB,SAAA;AACA,QAAA;YACEf,IAAAA,EAAM,iBAAA;YACNC,KAAAA,EAAO,kBAAA;YACPC,WAAAA,EACE,0HAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAM,aAAA;YAC3CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CC,YAAAA,kBAAAA,EAAoB,IAAMM,wBAAAA;AAC1BJ,YAAAA,mBAAAA,EAAqB,IAAMK,yBAAAA;YAC3BH,aAAAA,EAAeI;AACjB,SAAA;AACA,QAAA;YACElB,IAAAA,EAAM,oBAAA;YACNC,KAAAA,EAAO,qBAAA;YACPC,WAAAA,EACE,qKAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAe,aAAA;YACpDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQC;AAAK;AAAE;AAAC,aAAA;AAC7CG,YAAAA,mBAAAA,EAAqB,IAAMO,4BAAAA;YAC3BL,aAAAA,EAAeM;AACjB,SAAA;AACA,QAAA;YACEpB,IAAAA,EAAM,oBAAA;YACNC,KAAAA,EAAO,8BAAA;YACPC,WAAAA,EACE,oTAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAS,aAAA;YAC9CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMY,2BAAAA;AAC1BV,YAAAA,mBAAAA,EAAqB,IAAMW,4BAAAA;YAC3BT,aAAAA,EAAeU;AACjB,SAAA;AACA,QAAA;YACExB,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,+yDAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAO,aAAA;YAC5CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMe,0BAAAA;AAC1Bb,YAAAA,mBAAAA,EAAqB,IAAMc,2BAAAA;YAC3BZ,aAAAA,EAAea;AACjB,SAAA;AACA,QAAA;YACE3B,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,gyEAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAS,aAAA;YAC9CK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMkB,4BAAAA;AAC1BhB,YAAAA,mBAAAA,EAAqB,IAAMiB,6BAAAA;YAC3Bf,aAAAA,EAAegB;AACjB,SAAA;AACA,QAAA;YACE9B,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,sBAAA;YACPC,WAAAA,EACE,mRAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;;;;YAIrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQuB;AAAO;AAAE;AAAC,aAAA;AAC/CrB,YAAAA,kBAAAA,EAAoB,IAAMsB,4BAAAA;AAC1BpB,YAAAA,mBAAAA,EAAqB,IAAMqB,6BAAAA;YAC3BnB,aAAAA,EAAeoB;AACjB,SAAA;AACA,QAAA;YACElC,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,sBAAA;YACPC,WAAAA,EACE,8QAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;YACrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAMyB,4BAAAA;AAC1BvB,YAAAA,mBAAAA,EAAqB,IAAMwB,6BAAAA;YAC3BtB,aAAAA,EAAeuB;AACjB,SAAA;AACA,QAAA;YACErC,IAAAA,EAAM,mBAAA;YACNC,KAAAA,EAAO,oBAAA;YACPC,WAAAA,EACE,8VAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAc,aAAA;YACnDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAM4B,0BAAAA;AAC1B1B,YAAAA,mBAAAA,EAAqB,IAAM2B,2BAAAA;YAC3BzB,aAAAA,EAAe0B;AACjB,SAAA;AACA,QAAA;YACExC,IAAAA,EAAM,qBAAA;YACNC,KAAAA,EAAO,oCAAA;YACPC,WAAAA,EACE,yoCAAA;YACFC,SAAAA,EAAW;gBAAEC,MAAAA,EAAQ,QAAA;gBAAUJ,IAAAA,EAAM;AAAgB,aAAA;YACrDK,IAAAA,EAAM;gBAAEC,QAAAA,EAAU;AAAC,oBAAA;AAAEC,wBAAAA,MAAAA,EAAQC,QAAQa;AAAO;AAAE;AAAC,aAAA;AAC/CX,YAAAA,kBAAAA,EAAoB,IAAM+B,4BAAAA;AAC1B7B,YAAAA,mBAAAA,EAAqB,IAAM8B,6BAAAA;YAC3B5B,aAAAA,EAAe6B;AACjB;;AAGF;;;AAGC,IACM,MAAMC,sBAAAA,GAAyB,CAAC,EAAEC,MAAM,EAA2B,GAAA;;;;IAIxE,KAAK,MAAMC,QAAQ/C,6BAAAA,EAAAA,CAAiC;QAClD8C,MAAAA,CAAOE,EAAE,EAAEC,GAAAA,EAAKC,YAAAA,CAAaH,IAAAA,CAAAA;AAC/B,IAAA;AACF;;;;"}