Currently all configuration is scoped to a single MCP endpoint. Because of the size of Drupal and it's subsystems, I could see needing in the 100's of tools covering multiple phases of a projects life cycle and the need to adapt the available tools to the roles involved on a site.
An example would be:
I realize that this overlaps heavily with permissions, but the challenging part is just because someone has access to do something in the UI, doesn't necessarily mean that we want AI to have access to do the same thing. Whether it be AI being overzealous or security risks like prompt injection, being able to create more focused MCP servers would beneficial to some without impacting the experience of those using it as a single endpoint today.
Wrap the configuration in a config entity and create a default server during config install.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 2025-09-28 21.33.08.mp4 | 19.42 MB | jibla |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
gagosha commentedHey @michaellander, thanks for bringing this up. I agree, it's one of the must-have features and will be added to the top of the roadmap.
Comment #3
gagosha commentedComment #4
gagosha commentedComment #6
jibla commentedI am uploading the very brief screencast by @gagosha and changing the status of this issue to "needs review". We need thorough testing and creating upcoming issues related to this or comments down here.