QNAP MCP server issue: folder creation works, but no file-write tool is exposed

I’m testing a custom ChatGPT connector to a QNAP NAS using MCP Assistant.

The connector can successfully reach the NAS and list the root shared folders. It sees:

/AI
/Container
/home
/homes
/Public

It can also create folders successfully. For example, this worked:

/AI/chatgpt_write_test_20260622

The tunnel, authentication, File Station access, and NAS permissions appear to be working.

The problem appears to be that the MCP server only advertises these tools/actions to ChatGPT:

advanced_search
create_folder
list_files
search_files

There is no tool exposed for:

create_file
write_file
upload_file
read_file
delete_file
move_file
rename_file

Because of that, ChatGPT can create a folder but cannot create or modify files.

This looks like an MCP server/tool-definition issue rather than a QNAP permissions issue. The MCP server appears to expose only a limited subset of QNAP/File Station functionality. Also, changing the credentials read-only configuration does not change the tools advertised to ChatGPT. I would expect the MCP tools/list response to change based on the state of the read-only config.

Expected behaviour:

If read-only = true:
  expose only list/search/read tools

If read-only = false:
  expose list/search/read/write tools, including at least:
    create_folder
    write_file or upload_file
    read_file
    delete_file
    move_file/rename_file

Question for QNAP/MCP users:

Is this expected behaviour for the QNAP MCP server, or should it expose file-write/upload actions when read-only mode is disabled?