Use Single Tenant and Fix MCP Server Bug

[MikeAlhayek]

No description provided.

[Piedone]

I don't have much appetite reverting the configs for the tenant, it's fine.

[MikeAlhayek]

I don't have much appetite reverting the configs for the tenant, it's fine.

I think we should. A single tenant not multiple. + https://orchardcore.net/mcp read much better than https://mcp.orchardcore.net/mcp.

There is no advantage for running multiple tenants for this. At the end of the day MCP Server is just a feature in OC and we simplify by enable the feature on the main tenant and use better domain structure for consumers.

[MikeAlhayek]

@Piedone can't finish testing the MCP server until we merge this. Please review one more time.

[Piedone]

Will do.

[Piedone]

Yeah I still think it's better on a separate tenant. It needs different admins, there's no overlap in functionality with the homepage, we might want to restrict public access to the MCP on an infrastructure level or otherwise manage traffic differently, and if anything breaks with it it shouldn't affect the homepage. All easier with a separate tenant.

If you in particular dislike the double "mcp", then I suggest renaming the path in the module. Or, we can have ai.orchardcore.net/mcp, with other AI features possible to add in the future.

[MikeAlhayek]

Okay. Assign ai.orchardcore.com to the server please and I'll undo that change tomorrow.

Thanks

[Piedone]

Removed the McpServer tenant, added the AI one. Waiting for this so we can deploy it and I'll set it up.

[MikeAlhayek]

Closing this one in favor of #33