File Cabinet MCP Apps: AI Clients Can Now Browse, Upload, and Read File Cabinet Content

What changed

Three new MCP Apps ship inside the MCP Standard Tools SuiteApp, giving AI-client conversations direct access to the NetSuite File Cabinet:

• File Cabinet Browser MCP App — browse folders, search file names, upload files, and send supported file contents into an AI conversation.
• Get File MCP App — send a file's contents to the conversation by supplying its complete File Cabinet path. Prompts for confirmation before transmitting.
• Upload File MCP App — upload one or more files to a specified folder. Can auto-create missing subfolders when the role permits it.

Permission model

Access is controlled by two layers:

1. NetSuite role permissions — the user's role must already grant the relevant file/folder access.
2. Allowed File Cabinet Access — an account administrator must explicitly whitelist folders on the Custom Tools page (Configuring File Cabinet Access for Custom Tools). If this list is empty, all three apps are effectively disabled — no reads, uploads, or replacements will work.

Minimum access levels per operation:

• View — read an existing file
• Create — upload a new file
• Edit — replace an existing file

Upload constraints

• Files retain their original names on upload.
• Replacing an existing file requires the new file to have the same file type as the original.
• Existing text files with non-UTF-8 encoding cannot be replaced. All uploaded text files must be UTF-8.
• An upload can succeed even if the file's contents cannot subsequently be shared with or read by the AI client (e.g., unsupported binary formats).
• Browser-based uploads target the folder currently open in the app; the Upload File MCP App accepts a destination path.

Supported file extensions

Extension matching is case-insensitive. The full list:

• Documents & spreadsheets: .doc, .docx, .dot, .eps, .mpp, .pdf, .ppt, .pptx, .ps, .rtf, .vsd, .xls, .xlsx
• Images: .bmp, .gif, .ico, .icon, .jpeg, .jpg, .pjpeg, .png, .svg, .tif, .tiff
• Text: .log, .markdown, .md, .prn, .sql, .txt, .yaml, .yml
• Structured data & config: .config, .csv, .json, .xml, .xsd
• Web / scripts / templates: .appcache, .css, .ftl, .htc, .htm, .html, .js, .scss, .shtml, .ss, .ssp
• Archives: .gz, .tar, .zip
• Audio / video / animation: .mov, .mp3, .mpeg, .mpg, .swf
• CAD: .dwf, .dwg, .dwt, .dxf, .plt
• Certificates & keys: .cer, .crl, .crt, .csr, .der, .key, .p10, .p12, .p7b, .p7c, .p7r, .p8, .pem, .pfx, .spc
• Messages: .eml, .sms

What to do

1. Admin: configure allowed folders. Navigate to the Custom Tools page and populate Allowed File Cabinet Access with the folders AI clients should be able to reach. Without at least one entry, all three MCP Apps are non-functional.
2. Audit role permissions. Ensure users who will interact with MCP-connected AI tools have the appropriate File Cabinet permission levels (View / Create / Edit) on the whitelisted folders.
3. Plan for encoding. If your File Cabinet contains legacy text files in non-UTF-8 encodings (e.g., ISO-8859-1, Shift_JIS), be aware these cannot be replaced through the MCP upload path. Convert them to UTF-8 first if MCP-driven replacement is needed.
4. Review security posture. These apps expose File Cabinet contents — including certificates, keys, and configuration files — to AI-client conversations. Restrict the allowed-folder list to the minimum scope required. Sensitive folders containing .pem, .key, .pfx, or credentials should generally be excluded.

Note: Oracle's documentation does not specify which NetSuite release introduced these MCP Apps or the exact SuiteApp version. Verify availability in your account under SuiteCloud > Installed SuiteApps by searching for the MCP Standard Tools SuiteApp.