Bray
Give your coding agent a Nostr identity to post, DM, zap, and reason about trust on relays without hand-rolling protocol code.
Overview
dev.forgesworn/bray is a Build-phase MCP server that exposes 235 trust-aware Nostr tools for agent social, messaging, zaps, and identity.
What is this MCP server?
- 235 MCP tools across social posts, DMs, Lightning zaps, trust graphs, and identity
- Stdio npm package nostr-bray v1.27.7 with relay and key env configuration
- Optional Nostr Wallet Connect (NWC_URI) for zap workflows
- Trust-aware semantics aimed at autonomous agents, not generic REST wrappers
- 235 MCP tools documented for social, DMs, zaps, trust, and identity
- Server version 1.27.7 (npm identifier nostr-bray)
- Required env: NOSTR_SECRET_KEY, NOSTR_RELAYS; optional secret NWC_URI
What problem does it solve?
Building Nostr posting, DMs, zaps, and trust logic inside an agent loop means wrestling with keys, relays, and event kinds instead of shipping features.
Who is it for?
Builders shipping agent or API products that must live on Nostr relays with DMs, zaps, or trust scoring.
Skip if: Teams that only need a static marketing site or have no reason to hold Nostr keys in an agent environment.
What do I get? / Deliverables
After you register nostr-bray with keys and relays, your agent can call MCP tools for Nostr social and wallet flows without a custom client.
- Agent-callable Nostr social, DM, trust, and identity operations via MCP
- Optional Lightning zap flows when NWC_URI is set
- Live relay-backed participation without a hand-built Nostr client
Recommended MCP Servers
Journey fit
Nostr wiring lands in Build when you connect agent products to external networks and wallets, not during early idea research. Integrations is the canonical shelf for stdio MCP servers that expose a large third-party protocol surface to Claude Code and peers.
How it compares
Full Nostr MCP integration with 235 tools, not a single Claude skill or centralized social API wrapper.
Common Questions / FAQ
Who is dev.forgesworn/bray for?
It is for solo builders and small teams wiring AI agents into Nostr for social, private messages, Lightning zaps, and trust-aware identity.
When should I use dev.forgesworn/bray?
Use it during Build when your agent product needs real relay I/O—publish events, DM, zap, or evaluate trust—not during pure ideation.
How do I add dev.forgesworn/bray to my agent?
Install the npm package nostr-bray, set NOSTR_SECRET_KEY and NOSTR_RELAYS (and NWC_URI if zapping), add the stdio MCP entry in Claude Code or Cursor, then restart the session.