Nostr MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getProfileB | Get a Nostr profile by public key |
| getKind1NotesC | Get text notes (kind 1) by public key |
| getReceivedZapsC | Get zaps received by a public key |
| getSentZapsC | Get zaps sent by a public key |
| getAllZapsB | Get all zaps (sent and received) for a public key |
| getLongFormNotesC | Get long-form notes (kind 30023) by public key |
| searchNipsC | Search through Nostr Implementation Possibilities (NIPs) |
| sendAnonymousZapC | Prepare an anonymous zap to a profile or event |
| convertNip19B | Convert any NIP-19 entity (npub, nsec, note, nprofile, nevent, naddr) to another format |
| analyzeNip19C | Analyze any NIP-19 entity or hex string to understand its type and contents |
| postAnonymousNoteA | Post an anonymous note to the Nostr network using a temporary keypair |
| createKeypairC | Generate a new Nostr keypair |
| createProfileC | Create a new Nostr profile (kind 0 event) |
| updateProfileC | Update an existing Nostr profile (kind 0 event) |
| postNoteC | Post a note using an existing private key (authenticated posting) |
| createNoteC | Create a new kind 1 note event (unsigned) |
| signNoteC | Sign a note event with a private key |
| publishNoteC | Publish a signed note to Nostr relays |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have distinct purposes, but there is some overlap between createNote, postNote, publishNote, and signNote that could cause confusion about the note creation/publishing workflow. Tools like getAllZaps, getReceivedZaps, and getSentZaps are clearly differentiated, and other tools target specific resources or actions.
The naming is mixed with camelCase (e.g., analyzeNip19, convertNip19) and snake_case (e.g., get_long_form_notes, post_anonymous_note), and verb styles vary (e.g., 'create', 'get', 'post', 'publish', 'sign'). While readable, it lacks a consistent pattern throughout the set.
With 18 tools, the count is slightly high but reasonable for a Nostr server covering key management, note handling, profiles, zaps, and NIP utilities. It feels comprehensive without being overwhelmingly bloated, though it borders on the upper limit of typical scope.
The tool set provides complete coverage for the Nostr domain, including keypair creation, note creation/posting/publishing/signing, profile management (create, get, update), zap handling (send, get all/received/sent), NIP analysis/conversion/search, and anonymous operations. No obvious gaps are present for core workflows.