Hehe would believe me if I tell you I'm working on sometimes similar?

Reply to this note

Please Login to reply.

Discussion

Cool! Which part?

Various. Static pages using MCP as backend, for server side stuff, using contextvm, and also for serving them

Hmm, sounds interesting! Keep us updated! Let me know if you have something already working. 🔥

I had some experiments running. Serving a website, static or just proxying transparently any website through MCP using resource templates for the routing and path handling. Also dvmcp.fun could be seen as a static front end using dvms as the backend since you could call functionalities from MCP servers. I was going through a big refactor of dvmcp, now contextvm, and I'm looking forward to start playing in the other side of the project, apps

If I understand correctly ContextVM is an evolution of DVM, and spec to bring MCPs to nostr.

So you use that exactly for only server side stuff, or also for hosting the static files?

It is not necessarily an evolution of DVMS. The MCP is its own protocol, and ContextVM is the intersection between Nostr and MCP. However yes, you could replace the functionality of a DVMs using MCP.

It can be used for server-side stuff, where your MCP server exposes its capabilities over Nostr, such as tools, resources, and prompts, and consumed just using nostr events. It can also host static files as resources.

Thanks! I will check it deeper for my usecase!

I really like this concept of having a purely front end, and any server side logic is a DVM / ContextVM. This gonna be awesome!

The only missing feature for me is the nostr-deploy-servers variability, that any such server could be used to load any nostr webpages.