Connect another client

Any MCP client that speaks Streamable HTTP can connect: with OAuth sign-in if it supports it, or with an access token in a header.

With sign-in (OAuth)

Give the client the MCP URL, https://mcp.reliquary.redmage.cc/mcp (your Connect page shows the one to use). A client that follows the MCP authorization spec finds Reliquary's sign-in from the URL's first 401 answer, sends you to consent, and keeps its own refreshed tokens.

Reliquary identifies clients by a Client ID Metadata Document (an https URL); there is no dynamic client registration.

With a token

1. Create a token on the Tokens page with the vaults and access the client needs. Copy it; it is shown once.

2. Configure the client with the MCP URL and this header, reading the token from wherever the client keeps secrets:

   Authorization: Bearer <your token>
   

Tokens are for clients without sign-in: headless agents like Hermes, scripts, CI. Keep them out of chats and out of files an agent can read.

Check it

A tools/list call returns the tools in MCP tools. list_vaults returns the vaults the token reaches, with your role in each.

Environment variables

MCP never carries variable values. For a program that needs them, use the CLI: reliquary run or reliquary env pull. See Use the CLI.