💡 Request - Support for changing editor interfaces

[cachrisman]

Describe the solution you'd like
I'd like to use the mcp server to modify editor interfaces when creating or updating content types and adding fields.

I've been successful with a prompt like this

#contentful-mcp add a Nationality short text field with an 'in' validation of a predefined list of all nationalities and use the dropdown editor interface to the faculty content type

but I'm not really sure why the editor interface was correctly set to dropdown, maybe something with defaults??

but if I give a prompt like this:

add a Specialities short text list field with an 'in' validation with the following list as predefined choices:

Internal Medicine
Family Medicine
Pediatrics
OB/GYN
Psychiatry
General Surgery
Emergency Medicine

and use the checkbox editor interface

I get the field created properly with the intended validation, but the editor interface is the tagEditor which I think is the first in the list in the webapp making me think that the editor interface isn't being created at all and the webapp is filling in the missing info with the first editor interface in the list to choose from.

It became clear to me that editor interfaces weren't supported at all when (using the webapp) I had accidentally made an Image field as a entry reference field and not as a media field. I then gave the mcp server the following prompt:

change the Image reference field to be a media field with a validation to only select images

and it did it, but when loading an entry in the webapp, I get a warning that the selected widget cannot be used with this field, meaning the editor interface was still set to entryLinkEditor.

I then tried twice to get the mcp server to correct it to no avail.

the editor interface is incorrect for the Image field

and

the editor interface for the image field should be assetLinkEditor

and I was given this message

I apologize for the confusion. It seems I cannot directly set the editor interface through the field settings. Let me try a different approach:

I apologize for the confusion. I realize now that I need to use a different approach. The editor interface is managed separately from the content type definition. Let me know if you'd like me to continue trying to set up the assetLinkEditor for the image field.

[whitelisab]

Thank you for sharing your feedback @cachrisman! We’re logging this as feature request to support editor interfaces and will track it in our backlog. While we don’t have a timeline to provide at this point, we will update this thread once we have more clarity on when it may be delivered. In the meantime, contributions are welcome if you’d like to help move this forward.