nostr

Nostr

Use the bundled Nostr MCP server to read public Nostr data and, when a signer is configured, to act on Nostr.

Workflow

1. Resolve an identifier first when its type or relay hints are unclear (nostr_resolve_identity, nostr_resolve_handle for NIP-05 handles like [email protected]).
2. Use the most specific tool: nostr_get_profile, nostr_get_event, nostr_get_thread (full conversation), nostr_get_engagement (engagement totals), nostr_query_notes, or nostr_search_notes.
3. Check nostr_whoami before write operations to see which capabilities are enabled for the session.
4. Preserve relay provenance and mention partial relay failures when reporting results.
5. Treat an empty result as "not found on the queried relays," not proof that nothing exists anywhere on Nostr.

Writing

• Post with nostr_post_note; pass reply_to to reply, and threading tags get built automatically (NIP-10 for notes, NIP-22 comments for articles and other kinds). Attach uploaded media via attachments (imeta tags are built for you).
• Long-form goes to nostr_publish_article (markdown, kind 30023). Republishing with the same slug edits it.
• Save unfinished work with nostr_save_draft, then publish later with nostr_publish_draft.
• Reactions: "+" like, "-" dislike, or a single emoji. Deletion is best-effort and only works on your own events.
• Zaps need a configured wallet (nostr_wallet_status). Without one, use nostr_zap_invoice and give the user the Lightning invoice to pay manually. Always confirm amounts with the user before nostr_zap.

Media uploads

1. Call the exact Nostr tool named nostr_whoami in the runtime tool catalog (a host may display a qualified ID such as mcp__nostr__nostr_whoami). Require capabilities.mediaUpload to be true before uploading.
2. Call the exact catalog tool named nostr_upload_media (for example, mcp__nostr__nostr_upload_media when that is the host-visible ID) with mime_type and exactly one data source.
3. Use file_path only for a local file inside a server allowlisted NOSTR_MEDIA_UPLOAD_DIRS directory. Otherwise read the bytes without exposing secrets and send canonical base64 as data_base64.
4. Map the upload result into the destination tool:
   • For nostr_post_note, add one attachments item with url: result.url, mime_type: result.mimeType, size: result.size, and reuse the user-provided sanitized alt as alt when present. nostr_post_note builds the NIP-92 imeta tag itself.
   • For nostr_publish_article, pass only image: result.url; it has no attachment or imeta input.
5. imetaTag is returned metadata for clients that directly build Nostr events; do not pass it as an MCP tool input.