MCP setup

Install the pinned server

Node.js 22 or later is required. The preview package bundles its reviewed API dependency, so installation does not require access to a private repository. Install the downloaded tarball; no public npm package or managed multi-user endpoint is promised.

Install MCP 0.4.0

curl --fail --show-error --location --output reliquary-mcp-0.4.0.tgz \
  https://app.reliqua.ai/downloads/reliquary-mcp-0.4.0.tgz
npm install --global ./reliquary-mcp-0.4.0.tgz

Download MCP 0.4.0 — Pinned server package.

Release manifest — Checksums and supported releases.

Connect a stdio host

Add this entry to your MCP host configuration, then restart its connection. The command must be discoverable in the host process PATH; if your host does not inherit your shell PATH, select the installed command through its configuration. Hosts differ in where they store MCP configuration, so use the host's supported setup UI.

• Ask the assistant to call reliquary_connection and inspect its actual registered tools. A configured connection alone does not validate credentials or execution availability.
• Call reliquary_compute_catalog or reliquary_inventory for the first public result. No API key is required.
• Install the same official skills through the CLI only if your assistant supports skill directories; MCP works independently without installing the CLI.

MCP host configuration

{
  "mcpServers": {
    "reliquary": {
      "command": "reliquary-mcp",
      "env": {
        "RELIQUARY_ENABLE_WRITES": "false"
      }
    }
  }
}

Account scopes and execution

The existing server is single-account. For private reads, configure the applicable RELIQUARY_RESOURCES_KEY or RELIQUARY_TRAINING_KEY privately in the host environment. Credentials, account grants, live API support and qualified capacity remain distinct. Do not paste secrets into prompts or enable writes as part of this preview setup.

Authenticated HTTP transport remains available for a controlled single-account deployment with a separate MCP token and HTTPS proxy. It is not a public shared OAuth endpoint. This preview reuses the existing protocol and server-side authorization; it does not enable training, evaluation, generation or rental execution.

Authentication — Supported key scopes.

Errors and retries — Preserve original keys and reconcile unknown outcomes.