Nostr MCP

What AbdelStark/nostr-mcp MCP server does

AbdelStark/nostr-mcp MCP server exposes Nostr actions as tools that an MCP-compatible AI client can call. Its primary completed capability is publishing a new note to the Nostr network. The project also includes a Lightning zap tool for sending a payment to a Nostr user, although the README identifies that feature as work in progress.

The server is intended for agent workflows that need to publish short-form content to Nostr rather than only read or summarize external data. It can be useful for posting generated updates, announcements, or other notes from an AI-assisted application. The provided tools do not describe general feed search, note retrieval, profile management, or moderation functions.

How it works

At startup, the application loads its configuration from environment variables, including a list of WebSocket relay URLs and a Nostr private key. It uses those relays to connect to the Nostr network. MCP clients then invoke the exposed tools with structured inputs.

The post_note tool accepts a content value and publishes that text as a new note. The send_zap tool accepts a NIP-05-style address and an amount, represented in the example as nip05Address and amount. The README also documents Server-Sent Events as a supported transport for real-time communication.

AbdelStark/nostr-mcp MCP server is implemented in TypeScript and requires Node.js 18 or newer. Its source layout includes an entry point, a Nostr client implementation, and TypeScript type definitions.

Setup and configuration

Manual setup requires cloning the repository, entering its directory, and running npm install. The README provides npm run dev for development with hot reload and npm start for production startup. It also documents installation through Smithery for Claude Desktop, but that is a third-party installer rather than the project's own package command.

Configuration is supplied through a .env file. NOSTR_RELAYS contains comma-separated relay URLs, while NOSTR_NSEC_KEY stores the private key used for Nostr operations. SERVER_MODE selects the documented server mode, and PORT specifies the port for SSE mode. LOG_LEVEL controls logging verbosity, and NODE_ENV identifies the runtime environment.

The private key should be treated as a secret. The supplied example uses placeholder values, so they must be replaced with real configuration before the server can perform authenticated Nostr actions.

Tools and capabilities

• post_note: publishes a note using the supplied text content.
• send_zap: sends a Lightning zap to a Nostr user identified by a NIP-05 address and amount; this feature is marked WIP.
• Relay configuration: connects to multiple configured Nostr relays.
• SSE transport: provides Server-Sent Events support for MCP communication.

Limitations and notes

AbdelStark/nostr-mcp MCP server does not document read operations, search, profile updates, or other Nostr APIs beyond the two listed tools. Multiple simultaneous connections are listed as a future task. Configurable stdin transport is also listed as a TODO, so clients should not assume that mode is complete based only on the environment variable example.

The zap feature should be evaluated carefully before use in an automated payment workflow because the README labels it work in progress. Operation also depends on valid relay settings and a usable Nostr private key. The project is released under the MIT License.