Nostr MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Nostr MCP Server?

Nostr MCP Server is a Model Context Protocol (MCP) server that provides Nostr capabilities to large language models (LLMs) like Claude, enabling them to interact with the Nostr network.

How to use Nostr MCP Server?

To use the Nostr MCP Server, clone the repository, install dependencies, and configure it with applications like Claude for Desktop or Cursor. After configuration, you can make requests to interact with the Nostr network.

Key features of Nostr MCP Server?

  • Implements seven tools for Nostr network interaction, including fetching user profiles, notes, and zaps.
  • Supports both hex public keys and npub format for user identifiers.
  • User-friendly display of results with automatic format conversion.

Use cases of Nostr MCP Server?

  1. Fetching user profile information from the Nostr network.
  2. Retrieving text and long-form notes authored by users.
  3. Accessing detailed payment information for zaps sent and received.
  4. Searching through Nostr Implementation Possibilities (NIPs).

FAQ from Nostr MCP Server?

  • Can I use Nostr MCP Server with any LLM?

Yes! It is designed to work with LLMs like Claude and Cursor.

  • Is there a limit on the number of queries?

Yes, the server has a default 8-second timeout for queries to prevent hanging.

  • What formats are supported for user identifiers?

Both hex public keys and npub format are supported.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago