🇬🇪Georgia @gagosha

Hey @dan_metille,

Sorry for any inconvenience. We have our first release today, which should clarify the definition of 'soon'.

gagosha → created an issue.

gagosha → changed the visibility of the branch 3501988-create-mcp-plugin to hidden.

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

Hey, what do you think about the following suggestion, @ejb503 @jibla?

As a baseline, we all agree with what @marcus_johansson posted in the Slack channel: “It should be hostable by a normal webserver/PHP stack, without any additional layers needed.” Based on this, we can proceed as follows:

Requirement:

To implement an MCP server that directly connects to MCP clients, we need the following (simplified):

1. An SSE endpoint that allows clients to establish a connection and receive messages from the server. Method: GET.
2. A regular HTTP POST endpoint that enables clients to send messages to the server. Method: POST.

With this setup, the POST endpoint would run the operation and queue the result, which the GET request could then check and return.

Proposal:

What if we add a configuration form with just one checkbox (defaulted to true) that determines whether the POST request should queue the operation result or return it directly?

This approach would allow us to maintain both implementations without any additional work. The core of MCP would return results compatible with the specification, creating a win-win situation. By default, no additional layer is needed, and everything would be standard, straightforward, and directly hostable by Drupal.