1. Merge submodules into MCP module
This was suggested by Dries. Idea is to at this stage of the module make it easy to install and enable for people and collect all the tools that we develop into the main module.

So,

MCP <--- Extra
MCP <--- Dev Tools

Maybe its better for current and future maintenance, to keep those as separate modules, then think of other way how to simply make them enabled when the parent MCP module is enabled.

2. Move MCP configuration from "Web Services" into AI (/admin/config/ai/)
This was also suggested by Dries. From the technical point, it makes sense to be in web services, but from the context it belongs in the AI, as people will try to search it there.

3. Define the package "MCP" for all our modules and submodules (this is how it is grouped in the install list)

Issue fork mcp-3554528

Command icon 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:

About issue forks

Comments

jibla created an issue. See original summary.

gagosha made their first commit to this issue’s fork.

gagosha changed the visibility of the branch 3554528-changes-before-1.2.1 to hidden.

gagosha changed the visibility of the branch 3554528-changes-before-1.2.1 to active.

gagosha opened merge request !38

gagosha’s picture

gagosha commented
Assigned: gagosha » jibla
Status: Active » Needs review
gagosha’s picture

gagosha commented

Skipped moving MCP configuration from 'Web Services' into AI as it would require AI as a hard dependency, and it isn't. You can use MCP without AI (if needed), write custom tools, etc., and just expose it outside the LLM.

jibla’s picture

jibla commented

Sure. Lets merge this.

  • gagosha committed 104bafcb on 1.x 
    [#3554528] feat: Changes before 1.2.1 stable release
gagosha’s picture

gagosha commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.