Demo Time:

https://v.nostr.build/VWYvyenZa62dkGBi.mp4

Claude Desktop communicates with a local Nostr Model Context Protocol Server.

The MCP server looks for Nip89s of MCP enabled data vending machines and provides them as tools to the LLM. When Claude finds it adequate it calls a tool (asks the user if it's ok to use the tool) and the MCP server makes a NIP90 request to the DVM and gives back the answer to the LLM. The LLM builds us a nice report based on the real time data provided by a DVM living on Nostr (in the case I run it on the left screen).

nostr:nevent1qqsx07t2rwzvae6tumn5j6lvugp79psyz27z9k53lw4h2jekszrgejqpz9mhxue69uhkummnw3ezuamfdejj7q3qr0d8u8mnj6769500nypnm28a9hpk9qg8jr0ehe30tygr3wuhcnvsxpqqqqqqz4q0990

Reply to this note

Please Login to reply.

Discussion

Incredible stuff!

This gives MCP Servers a way of discovery via Nip89 on Nostr

It also allows MCP clients to use remote Servers today, which is only limited or not at all supported in most clients right now.

This MCP stuff is over my head, need to get it on the backlog to learn once I finish releasing the toolset I have today.

This is happening and believe the hype or not, this is bullish AF. I also cooked (slowly) during the week, planning to release some updates to the dvmcp packages over the weekend. If you still don't know what dvmcp is and are afraid to ask, I wrote an article last weekend that kickstarted this idea, which is now about to blossom

https://njump.me/naddr1qvzqqqr4gupzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qq24z4rp09mkzk290p25x5zyd3uk5at6da545c3ea4m

Also the repo github.com/gzuuus/dvmcp

nostr:nevent1qqspwzfy76828l7d27920rymax5g6euxkjaa9fumnxshx2nq4rdverqpz9mhxue69uhkummnw3ezuamfdejj7q3qnxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjqxpqqqqqqz0y0zn2

that's fucking sick