Nostr MCP Server

What jorgenclaw/nostr-mcp-server MCP server does

The jorgenclaw/nostr-mcp-server MCP server connects MCP-compatible AI clients to the Nostr protocol. It can create unsigned events, sign them, publish them to relays, and retrieve profiles or events. Higher-level operations cover text notes, profiles, follows, unfollows, reactions, reposts, deletions, replies, relay lists, and encrypted direct messages.

The tool set supports both common Nostr workflows and arbitrary event kinds. For example, an agent can create a text note and publish it, or build an event first and handle signing and relay publication as separate steps. Profile operations use kind 0 events, reactions use kind 7, reposts use kind 6, deletions use kind 5, and relay lists use NIP-65.

How it works

Signing can use one of two modes. In direct key mode, signing calls receive a privateKey parameter. In NIP-46 bunker mode, the server uses a configured bunker URI and routes signing through a compatible remote signer. The README describes this as a way to keep private keys out of the AI context; supported bunker examples include nsecbunker and Amber.

The server communicates with Nostr relays through WebSocket connections and exposes its functions using the Model Context Protocol. The repository documents a Streamable HTTP endpoint at https://nostr.jorgenclaw.ai/mcp and a legacy SSE endpoint at https://nostr.jorgenclaw.ai/sse. The supplied listing also identifies a Lightning-paid signing endpoint and describes per-call sat charges for signing and publishing operations, so deployment or endpoint terms should be checked before use.

Setup and configuration

For local use, clone the repository, install its npm dependencies, build the project, and start the generated entry point:

npm install
npm run build
node dist/index.js

Without bunker configuration, signing tools expect a privateKey value on each applicable call. For bunker mode, set NOSTR_BUNKER_URI to a URI containing the bunker public key, relay, and optional secret before starting the process:

NOSTR_BUNKER_URI="bunker://bunker-public-key?relay=wss://relay.example.com&secret=abc" node dist/index.js

The placeholder values in that example must be replaced with an actual NIP-46 configuration. The README states that the privateKey parameter becomes optional when bunker mode is active.

Tools and capabilities

jorgenclaw/nostr-mcp-server MCP server includes tools for:

• Creating, signing, and publishing notes or arbitrary Nostr events.
• Creating and updating profiles, following or unfollowing public keys, and managing relay lists.
• Reacting to, reposting, deleting, and replying to events with NIP-10 threading.
• Encrypting messages with NIP-04 or NIP-44 and sending DMs using either scheme.
• Inspecting signer mode and public key with getSignerInfo.
• Fetching profiles and events from relays.

The repository lists Claude Desktop, Cursor, Glama, Smithery, and other MCP clients as compatible with the Streamable HTTP transport. The supplied client requirements specifically include Claude Desktop and Cursor.

Limitations and notes

The server depends on access to Nostr relays for publication and retrieval. NIP-46 mode also requires an available compatible bunker or remote signer. Direct key mode places responsibility for supplying and protecting the private key on the caller.

The project is licensed under MIT. Its dependencies include nostr-tools, the MCP SDK, ws, and zod; these are implementation dependencies rather than separate services to install as the MCP server itself. The listing describes Lightning charges for certain signing and publishing calls, while the README also documents a locally runnable open-source deployment, so cost depends on the endpoint or deployment path used.