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

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.

Reply to this note

Please Login to reply.

Discussion

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.