This is an idea worth discussing...
When developing tests MCP Apps, I realized that those MCP Apps, where:
- Mingling UI-resources / MCP Apps and MCP Server together
- Targeting REACT developers
However, in the Reshapr approach:
- We emphasize reuse of existing API and SoC, so UI-resources / MCP Apps come way after the endpoints
- Other teams may produce UI-resources / MCP Apps - and are not specifically REACT-based teams.
For producing the two apps, I followed the same approach:
- Having a minimalist local HTTP server for UI development,
- Using the same structure and build for packaging the MCP Apps
- Have no dependency on REACT or other frameworks (they could be added later on though)
- Build a
Resources artifact that follows the same template.
We could imagine having a simple line command tool that automates the initialization of all of this and offers a quick start for non-expert teams...
2 different approaches are possible:
As of today, I prefer the Bootstrap way of doing things because: no need to install anything upfront and once executed, there's no traces of it anywhere.
This is an idea worth discussing...
When developing tests MCP Apps, I realized that those MCP Apps, where:
However, in the Reshapr approach:
For producing the two apps, I followed the same approach:
Resourcesartifact that follows the same template.We could imagine having a simple line command tool that automates the initialization of all of this and offers a quick start for non-expert teams...
2 different approaches are possible:
reshaprCLIAs of today, I prefer the Bootstrap way of doing things because: no need to install anything upfront and once executed, there's no traces of it anywhere.