Bray MCP Server

Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity

Local serverstdio

What is the Bray MCP server?

Connect Bray to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity. The bray mcp server is what makes that connection.

What the server does

New to Nostr? Mint a key first -- this works before anything is configured and prints your npub plus a 24-word mnemonic (write it down; it is the key):

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Name — - "alice" (resolved from your dispatch contacts)
  • NIP-05 — - "alice@example.com" (HTTP lookup)
  • npub — - "npub1abc..." (NIP-19 decode)
  • Hex — - "a1b2c3..." (64-character passthrough)
  • Tier — Method
  • Heartwood — Dedicated signing appliance (BUNKER_URI)
  • ncryptsec — NIP-49 encrypted key (NOSTR_NCRYPTSEC)
  • Group — Tools
  • Identity — 16
  • Social — 15
  • Trust — 22
  • Dispatch — 13

Installation

The server ships on npm as nostr-bray, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: NOSTR_SECRET_KEY, NOSTR_RELAYS, BUNKER_URI. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bray's toolset — Name, NIP-05, npub and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dev.forgesworn; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Bray's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Bray.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Name- "alice" (resolved from your dispatch contacts)
NIP-05- "alice@example.com" (HTTP lookup)
npub- "npub1abc..." (NIP-19 decode)
Hex- "a1b2c3..." (64-character passthrough)
TierMethod
HeartwoodDedicated signing appliance (BUNKER_URI)
ncryptsecNIP-49 encrypted key (NOSTR_NCRYPTSEC)
GroupTools
Identity16
Social15
Trust22
Dispatch13
Relay13
Moderation16

How to install the Bray MCP server

Add to your MCP client config:

```json
{
  "mcpServers": {
    "nostr": {
      "command": "npx",
      "args": ["nostr-bray"],
      "env": {
        "NOSTR_SECRET_KEY": "nsec1...",
        "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
NOSTR_SECRET_KEYCredential the server authenticates with.Yes
NOSTR_RELAYSConfiguration value read at startup.Optional
BUNKER_URIConfiguration value read at startup.Optional

Example prompts to try

  • Use Bray to Name.
  • Use Bray to NIP-05.
  • Use Bray to npub.

Frequently asked questions

It connects Bray to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Name, NIP-05, npub, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Bray directly.