Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP server for Nostr posting and zaps
This is a Nostr connector for MCP clients. It lets an agent connect to one or more relays, post notes, and send Lightning zaps through the Nostr network. The server supports SSE transport now, with stdio listed as a planned mode. Configuration comes from environment variables like relay URLs, an `nsec` key, and the server mode.

Builders who want Claude or another MCP client to post to Nostr and send zaps.
You can have your agent publish to Nostr and interact with the network without leaving your workspace.
What it does
Post notes
Provides a `post_note` tool that sends a new note to Nostr.
Send zaps
Provides a `send_zap` tool for Lightning payments to a Nostr user by NIP-05 address.
Multiple relays
Connects to a configurable list of Nostr relays from the environment.
MCP transport support
Runs with SSE transport now and has a stdio server entry point in the codebase.
How to get it
- 1To install Nostr MCP Server for Claude Desktop automatically via Smithery
npx -y @smithery/cli install @AbdelStark/nostr-mcp --client claude
- 2Clone the repository
git clone https://github.com/AbdelStark/nostr-mcp cd nostr-mcp
- 3Install dependencies
npm install
- 4Run
# Development mode with hot reload npm run dev # Production mode npm start
README
π Nostr MCP Server
A Model Context Protocol (MCP) server that enables AI models to interact with Nostr, allowing them to post notes and interact with the freedom of speech protocol.
Censorship resistance matters, even for LLMs.
BTW, you should join Nostr now!
π Features
- π Post notes to Nostr network
- π Connect to multiple relays
- π€ MCP-compliant API for AI integration
- πΈ Send Lightning zaps to Nostr users (WIP)
- π‘ Server-Sent Events (SSE) support for real-time communication
π·ββοΈ TODOs
- Add support for multiple simultaneous connections
- Implement stdin transport mode (configurable via environment variable)
π Prerequisites
- Node.js 18+
π οΈ Installation
Installing via Smithery
To install Nostr MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @AbdelStark/nostr-mcp --client claude
Manual Installation
- Clone the repository:
git clone https://github.com/AbdelStark/nostr-mcp
cd nostr-mcp
- Install dependencies:
npm install
- Create a
.envfile:
π‘ You can copy the
.env.examplefile and modify it as needed.
# Log level (debug, info, warn, error)
LOG_LEVEL=debug
# Node environment (development, production)
NODE_ENV=development
# List of Nostr relays to connect to
NOSTR_RELAYS=wss://relay.damus.io,wss://relay.primal.net,wss://nos.lol
# Your Nostr private key (starts with nsec)
NOSTR_NSEC_KEY=your_nsec_key_here
# Server mode (stdio or sse)
SERVER_MODE=sse
# Port for SSE mode
PORT=9000
π¦ Usage
Starting the Server
# Development mode with hot reload
npm run dev
# Production mode
npm start
Available Tools
post_note
Posts a new note to the Nostr network.
Example input:
{
"content": "Hello from Nostr! π"
}
send_zap
Sends a Lightning zap to a Nostr user.
Example input:
{
"nip05Address": "user@domain.com",
"amount": 1000
}
π§ Development
Project Structure
nostr-mcp/
βββ src/
β βββ index.ts # Main server entry point
β βββ nostr-client.ts # Nostr client implementation
β βββ types.ts # TypeScript type definitions
βββ .env # Environment configuration
βββ tsconfig.json # TypeScript configuration
Running Tests
npm test
π€ Contributing
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
π License
This project is licensed under the MIT License - see the LICENSE file for details.
π Resources
- Join Nostr
- Nostr Manifesto
- Nostr Specifications
- Model Context Protocol
- Visual testing tool for MCP servers
- Awesome MCP Servers
- Awesome MCP Clients
- MCP TypeScript SDK
- Nostr Development Kit (NDK)
π¬ Contact
Feel free to follow me if you'd like, using my public key:
npub1hr6v96g0phtxwys4x0tm3khawuuykz6s28uzwtj5j0zc7lunu99snw2e29
Or just scan this QR code to find me:

Made with β€οΈ for the Nostr community
Files in the repo
- .github
- .husky
- src
- .env.example
- .eslintrc.cjs
- .gitignore
- .lintstagedrc.json
- .prettierrc
- Dockerfile
- jest.config.js
- LICENSE
- package-lock.json
- package.json
- README.md
- smithery.yaml
- tsconfig.json
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph β average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code β use any LLM (Claude, Gemini, Grok, DeepSeek, Ollamaβ¦) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300Β΅s in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Stop your AI from making things up β it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.
x64dbg-MCP Server is a native MCP (Model Context Protocol) plugin for x64dbg that exposes the debugger's full functionality over HTTP. Connect any MCP-compatible AI assistant and control x64dbg programmatically: set breakpoints, step through code, read memory, dump registers, and more. Built with Zig β zero dependencies, single-binary output, cros