Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Currently there is a hard dependency to the AI and AI Agents module, because that is historically been used for this.
However when #3557644: Use Tool API is merged, we do not have a hardcoded dependency anymore and as soon as Tool API works with ECA, we have a way to work with the MCP Client without using AI. In theory you could already do it programtically.
Proposed resolution
Remove the AI and AI Agents from composer.
Move the route item to be under web services instead (workflows?).
| Comment | File | Size | Author |
|---|
Issue fork mcp_client-3559613
Show commands
Start 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 #3
marcus_johansson commentedComment #4
robertoperuzzoYou are right to remove the dependency, and it works in my local ddev environment.
I would propose this straightforward method for dynamically discovering the operation's type.
What do you think about it?
Comment #5
marcus_johansson commentedThanks - I've created a follow up issue for that here #3559869: Set tool operation per tool.
But I think we should have #3537086: Lock title and descriptions as well, since it can build on this.
Will merge this then.
Comment #6
robertoperuzzo