Nrtsearch MCP Server

Connect Nrtsearch to Claude, Cursor or any other MCP client and it stops being a tab you switch to. This will: - Install all dependencies (including MCP SDK) - Start the server on the configured port. The nrtsearch mcp server is what makes that connection.

What the server does

• Exposes NRTSearch/Lucene search as a robust MCP server for AI tools
• Accepts any Lucene query (Boolean, phrase, range, wildcard, fuzzy, etc.)
• Structured logging, retries, and highlight support
• Pure unit-testable search logic with full test coverage
• Easy integration with GitHub Copilot, Claude Desktop, and other MCP clients
• Modern Python packaging and configuration (Pydantic, pyproject.toml)

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

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

• text — (irish AND pub AND (texas OR tx))
• stars — [4 TO 5] AND text:(vegan AND brunch)

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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Nrtsearch's toolset — text, stars — is a fair guide to whether it matches your workflow. It is maintained by tvergilio; worth a glance at recent repository activity before you build anything load-bearing on it.

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