local embedder is a separate, fully offline
package (@the-40-thieves/reliquary-tc-embedder-local) that npm install does not include;
reliquary-tc setup offers to install it, and once it is installed it needs no config file, no
Ollama, and no API key (one-time model download on first use). The table below says
which install methods carry it; Embeddings has the detail.
Ollama and every hosted provider (OpenAI, Voyage, Cohere, …) are opt-in either way — a
config file is what selects one, and is also the upgrade for ACLs, HITL, the generative
tier, and everything else — see First Run.
reliquary-tc ships in several forms. All of them run the same server; pick whichever
fits your environment.
What works out of the box, per install method
Measured, not assumed: CI installs each path on a clean Ubuntu, macOS and Windows machine, points it at a vault with no config file, and runs a real semantic search (ci-first-run-smoke). The npm cell requests the embedder by name, because npm does not install it by default. Every cell passes on Ubuntu, on Apple Silicon macOS and on Windows. On Intel
macOS (macos-15-intel, macos-26-intel) ONNX Runtime publishes no native build, so npm, .mcpb,
and the standalone binary run the local embedder on ONNX Runtime’s WASM backend instead, with the
same models. WASM embedding is roughly 4x slower than native in the measured two-text probe.
The model weights are not in any of them: the first search downloads and checksum-verifies
them (about 140 MB) into the cache directory, then works offline.
npm (Node 24+)
reliquary-tc binary backed by the published reliquary-tc
package and its @the-40-thieves/reliquary-tc-{shared,native} companions. The
native module ships prebuilds for eight targets — linux-x64-gnu,
linux-arm64-gnu, linux-x64-musl, linux-arm64-musl (Alpine), darwin-x64,
darwin-arm64, win32-x64-msvc, and win32-arm64-msvc; on any other platform it
transparently falls back to a pure-JS implementation.
The local embedder is opt-in: npm install -g reliquary-tc does not install it. If you use Ollama
or a hosted embeddings provider, you do not need it. For the default local embedder, install the
same version as reliquary-tc (reliquary-tc --version):
reliquary-tc setup offers to run this install for you. npm then installs the embedder’s generated
base package plus only @the-40-thieves/reliquary-tc-embedder-local-<os>-<arch> for the host. It
does not install @huggingface/transformers or the other platforms’ ONNX binaries. Installing it
with --omit=optional or --no-optional leaves out that host runtime.
Standalone binary
Each release attaches self-contained executables (built withbun build --compile,
bytecode + minified) that bundle the runtime, so no Node or Bun is required on the
host. Targets: macOS x64 + arm64, Windows x64, and Linux x64 + arm64. Download the
asset for your platform from the GitHub release and run it directly. (Windows on
arm64 is not a bun --compile target; use the npm install there.)
The bundled local embedder runs from inside the binary: it is compiled in with its selected ONNX
runtime, whose native files or macOS x64 WASM assets are unpacked into the cache directory
(<cacheDir>/runtime/) on first use, so semantic search works with no config file. That adds about
14 MB to the file. Intel macOS uses WASM, measured at roughly 4x slower embedding than native. The
local reranker cannot run from a binary, and the pure-JS fallback replaces the native addon;
lexical search is unaffected.
Docker
oven/bun:1.4.2-slim build (Debian, glibc): the native prebuilds are
gnu, so a glibc base keeps them loadable instead of forcing the pure-JS fallback. The
image carries the built local embedder next to the server, so the default local
provider resolves with no extra install. The model weights are not in the image: the
first search downloads them into the cache directory. The command above puts the cache
on the named volume reliquary-tc-cache (RELIQUARY_TC_CACHE_DIR sets cacheDir), so
the weights and the index survive --rm and a new container. Without that volume every
new container downloads the weights and rebuilds the index. More in
Docker deployment.
One-click bundle (.mcpb)
For MCPB-capable MCP hosts, each release attaches a one-click reliquary-tc.mcpb
bundle. It runs the server under the host’s Node (24+) and is self-contained: no
node_modules and no native build are required on the machine. It carries sqlite-vec
for every platform (loaded through Node’s built-in node:sqlite, so the dense index is on)
and the bundled local embedder with native ONNX Runtime for Linux x64 and arm64, macOS arm64 and
Windows x64, plus ONNX Runtime Web WASM for macOS x64. Semantic search therefore works with no
config file on every current target. Because one bundle serves every OS, it uses the pure-JS
fallback instead of the native addon, and it is about 66 MB.
Install it through your host’s MCP-bundle installer.
Anthropic’s connector directory no longer accepts local servers packaged as .mcpb
(its submission guide, read
2026-10-10, sends local servers through a plugin). The bundle still installs by hand in
Claude Desktop and other MCPB hosts; the plugin below is the route for Claude’s directory.
Claude Code plugin and other agents
The repository is also a Claude-style plugin marketplace. The plugin launches the published package over stdio (npx -y reliquary-tc) and asks for your config file path
when you enable it, passing it to the server as RELIQUARY_TC_CONFIG.
/plugin marketplace add The-40-Thieves/reliquary-tc.
Node 24+ must be on PATH for npx.
- Grok Build documents that it reads Claude Code marketplaces, plugins and MCP servers
with no extra setup (docs.x.ai,
read 2026-10-10). Its docs do not say which files it reads, and the
${user_config.*}substitution is a Claude Code feature, so if the server starts with a literal placeholder as its config path, setRELIQUARY_TC_CONFIGyourself in a.grokMCP entry. - Muse Code (1.4.0 and later) has a plugin system that third-party write-ups report sits
behind
MUSE_EXPERIMENTAL_PLUGINS=1. It reads the same marketplace file, and the plugin carries a.muse-plugin/plugin.jsonwith the server undercapabilities.mcpServers. Meta’s published Muse Code docs do not yet describe the plugin format, so that manifest follows the shape existing Muse plugins use and has not been run throughmuse plugins validatehere. ExportRELIQUARY_TC_CONFIGin the shell that starts Muse; the manifest has no place to prompt for it.
claude.ai and Claude Desktop (remote HTTP)
claude.ai has no install deep link. For a server you host over Streamable HTTP, add it as a custom connector: Customize > Connectors > + Add > Add custom connector, enter the name and the server’shttps:// MCP URL (for example https://your-host/mcp), then set the
authentication the server uses (see Auth). Team and Enterprise
owners add it under Organization settings > Connectors. Source:
Anthropic’s custom connector guide,
read 2026-10-10.
Use the /mcp/core URL where a client or directory wants a flat tool list with no
generic executor; every tool on it states readOnlyHint, destructiveHint and
openWorldHint explicitly.
Companion plugin
Tools that bridge into a live Obsidian instance (Dataview, Templater, OCR, command execution) require the companion plugin, TC Bridge, which exposes the vault’s Local REST API. Install it from Obsidian’s Community Plugins browser (search “TC Bridge”, or go directly to community.obsidian.md/plugins/tc-bridge) and enable it. The release’s plugin zip, extracted into.obsidian/plugins/, is
the manual fallback for hosts that can’t reach the community directory. The
server runs without it either way — those bridge tools simply degrade to
plugin_missing.
Next: First Run.