SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI marketingnostr-mcp-server

nostr-mcp-server

Sign and publish Nostr events, paid per call in sats over Lightning.

Open website

About this tool

Purpose

nostr-mcp-server is a Model Context Protocol (MCP) server used to provide AI agents with Nostr protocol capabilities. Its core design goal is to keep private keys out of the AI's context window through NIP-46 remote signing support.

Main capabilities

  • Supports NIP-46 remote signing (bunker mode).
  • Can be connected to directly without running locally; the transport is Streamable HTTP (MCP specification 2025-03-26), compatible with Claude Desktop, Cursor, Glama, Smithery, and any MCP client.
  • Provides a legacy SSE endpoint for backward compatibility.
  • Provides 23 tools, including notes, profiles, social actions, direct messages (NIP-04/44), relay lists, zap, and fetch.
  • Supports two signing modes: NIP-46 bunker mode (set NOSTR_BUNKER_URI once, and all signing goes through the bunker) and direct key mode (pass privateKey in each tool call, for backward compatibility).
  • Compatible with nsecbunker, Amber, and any NIP-46 signer.
  • Provides a NIP-05 identity service: an AI agent can pay via the Lightning Network to register yourname@jorgenclaw.ai as a verified Nostr identity.

Usage

Remote connection address: Streamable HTTP (MCP specification 2025-03-26); legacy SSE endpoint:https://nostr.jorgenclaw.ai/sse

NIP-05 identity registration process:

  1. Open any Nostr client (Amethyst, Primal, Damus, etc.)
  2. Send a direct message to this npub: npub16pg5zadrrhseg2qjt9lwfcl50zcc8alnt7mnaend3j04wjz4gnjqn6efzc
  3. Send the message: register yourname
  4. Pay the Lightning Network invoice received in the reply (1,000 sats)
  5. Done; yourname@jorgenclaw.ai will resolve immediately in all Nostr clients. This process uses NIP-17 gift-wrapped direct messages and works with all modern Nostr clients.

NIP-46 Bunker URI format: bunker://<bunker-hex-pubkey>?relay=wss://relay.com&secret=optional

Applicable scenarios

Suitable for developers and users who want to give AI agents Nostr interaction capabilities while avoiding exposure of private keys to the AI context window, for example publishing Nostr notes, social interaction, direct messages, relay list management, zap, and data fetching through MCP clients.

Limitations

  • Direct key mode requires the privateKey parameter in every signing call; in bunker mode this parameter is optional.
  • NIP-05 identity registration requires payment of a 1,000 sats Lightning Network fee.
  • The material mentions another "Sovereign MCP (paid)" service: 9 tools, per-call billing in sats, provides LCS-1 operation receipts, and requires no registration, but its specific relationship to nostr-mcp-server and integration details are not yet provided.
  • Apart from the above, no other functionality, pricing, platform, effect, or step information is currently provided.

Related tools

Browse category