Nostrdb — query and analyze local Nostr data with fast, private integrations for developers and researchers.
Enable Claude to query your database directly using natural language
Example: Ask 'Show me top 10 customers by revenue this month' and get SQL results instantly
Eliminate manual SQL writing for ad-hoc queries, get insights 10x faster
Generate complex reports and analytics without leaving conversation
Example: Analyze sales trends, cohort retention, user behavior patterns conversationally
Democratize data access—non-technical team members can query databases
Understand database structure, relationships, and data models
Example: 'Explain the user_orders table schema and its relationships'
Onboard engineers faster, explore unfamiliar databases efficiently
Run data quality queries to catch anomalies and inconsistencies
Example: Find duplicate records, missing values, orphaned foreign keys automatically
Maintain data integrity with less manual SQL work
Extend
Turn documents into structured data
OneSignal
Agentic access to OneSignal’s customer engagement platform for messaging, users, and analytics.
Harness
Build, Ship and Secure your apps on Harness Platform
Craft.io
Manage your end-to-end product lifecycle - backlog, PRDs, customer feedback, roadmaps, and strategic OKRs - with Claude connected directly to your Craft.io data.
MDN
Search & retrieval of MDN docs & browser compat data
Sprites
Let Claude manage your Sprites
Useful MCP listing: Nostrdb is the kind of server we cite when onboarding engineers to host + tool permissions.
Nostrdb reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: Nostrdb surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Nostrdb has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Nostrdb benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Nostrdb into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Nostrdb reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Nostrdb is the kind of server we cite when onboarding engineers to host + tool permissions.
Nostrdb is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Nostrdb against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 54
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"nostrdb-mcp": {
"command": "npx",
"args": [
"-y",
"nostrdb-mcp"
]
}
}
}Provides access to locally stored Nostr social network data through nostrdb database queries. Works with your existing Notedeck data to search and analyze Nostr posts and events.
Nostrdb is a community-built MCP server published by damus-io that provides AI assistants with tools and capabilities via the Model Context Protocol. Nostrdb — query and analyze local Nostr data with fast, private integrations for developers and researchers. It is categorized under databases, developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install Nostrdb in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
README content is unavailable from source data for this server.
Open GitHub repository →Time estimate: 15-30 minutes including configuration and testing
Prerequisites
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server acts as bridge between Claude and database, translating natural language to SQL queries and returning results in structured format.
Protocols
Compatibility
✓ Use when
Use for ad-hoc data queries, exploratory analysis, report generation, schema exploration, and democratizing data access. Best for read-heavy analytics workloads.
✗ Avoid when
Avoid for production write operations, mission-critical transactions, real-time OLTP workloads, or when database contains sensitive PII without proper access controls. Use read replicas, not primary.