# Reliquary

> Reliquary is a shared vault of context and environment variables for people and the AI agents they use, over one MCP URL.

Each page below is Markdown. Everything in one file: https://reliquary.redmage.cc/llms-full.txt

## Start here

- [Reliquary docs](https://reliquary.redmage.cc/docs/index.md): Reliquary is a shared vault of context and environment variables for people and the AI agents they use, over one MCP URL.

## Tutorials

- [Getting started](https://reliquary.redmage.cc/docs/tutorials/getting-started.md): Create a vault, connect Claude Code, approve your agent's first proposal, then run a command with your first environment variable.

## Concepts

- [Vaults, files and folders](https://reliquary.redmage.cc/docs/concepts/vaults-and-files.md): A vault is the container for one team, client or project: its files, its environment variables, its members and its activity log.
- [Vault templates](https://reliquary.redmage.cc/docs/concepts/templates.md): A template starts a new vault with folders, rules and a README that tells agents how to work in it, so you and your agents don't begin from an empty page.
- [Canon, open and rules](https://reliquary.redmage.cc/docs/concepts/canon-and-rules.md): Every file is either canon, which changes only when enough people approve, or open, which members and their agents write directly.
- [Proposals and review](https://reliquary.redmage.cc/docs/concepts/proposals-and-review.md): A proposal is a suggested change to a file, usually a canon one, that waits for people to approve, request changes or reject it.
- [Agents and the ceiling](https://reliquary.redmage.cc/docs/concepts/agents.md): An agent you connect acts as you, with your role in each vault, except for a short list of actions that need you present in the web app.
- [Tokens, connections and sign-ins](https://reliquary.redmage.cc/docs/concepts/connections.md): Three kinds of credential let software act for you, and all of them are listed on your Tokens page, where you can revoke any of them.
- [Environment variables](https://reliquary.redmage.cc/docs/concepts/variables.md): A vault holds shared environment variables per environment, delivered to your programs by the CLI and never to a model.
- [Imports](https://reliquary.redmage.cc/docs/concepts/imports.md): An import brings a whole `.env` file into a vault at once, and nothing is set until a person applies it in the web app.
- [Members and invites](https://reliquary.redmage.cc/docs/concepts/members.md): People join a vault only by invite, with a role an owner picks, and only the owner of a vault manages who is in it.
- [Activity](https://reliquary.redmage.cc/docs/concepts/activity.md): Every change in a vault is recorded in its activity log, which nobody can edit or delete.
- [Export, delete and erase](https://reliquary.redmage.cc/docs/concepts/export-delete-erase.md): Your data can leave: an owner can export a vault, delete it at once, or erase a single file's text, each in person, behind a confirm step.
- [Plans and limits](https://reliquary.redmage.cc/docs/concepts/plans-and-limits.md): Your account's plan limits how many vaults you own. Each vault's tier limits how many people it holds and how much it stores. Nothing is billed yet.
- [Security model](https://reliquary.redmage.cc/docs/concepts/security.md): Reliquary's rules live in the database, each has a hostile test, secret values are encrypted with a key the database never holds, and the limits of all that are stated plainly.

## How-to guides

- [Connect Claude Code](https://reliquary.redmage.cc/docs/how-to/connect-claude-code.md): Add Reliquary to Claude Code once per computer, then sign in from Claude Code; no token to copy.
- [Connect Claude.ai](https://reliquary.redmage.cc/docs/how-to/connect-claude-ai.md): Add Reliquary to Claude.ai as a custom connector, then sign in to Reliquary to allow it.
- [Connect ChatGPT](https://reliquary.redmage.cc/docs/how-to/connect-chatgpt.md): Add Reliquary to ChatGPT as a connector with OAuth, then sign in to Reliquary to allow it.
- [Connect Cursor](https://reliquary.redmage.cc/docs/how-to/connect-cursor.md): Cursor connects with an access token that it reads from an environment variable, so the token never sits in a config file.
- [Connect VS Code](https://reliquary.redmage.cc/docs/how-to/connect-vs-code.md): VS Code connects with an access token that it asks for once and keeps in its secret storage.
- [Connect another client](https://reliquary.redmage.cc/docs/how-to/connect-other-clients.md): 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.
- [Use the CLI](https://reliquary.redmage.cc/docs/how-to/use-the-cli.md): Sign a computer in once, then run commands with a vault's variables, write them to a gitignored `.env`, or send a `.env` for approval.
- [Move a .env into a vault](https://reliquary.redmage.cc/docs/how-to/move-env-into-vault.md): Bring a project's existing `.env` into a vault, by paste or with `reliquary env push`, then run the project with `reliquary run` and retire the file.
- [Invite someone](https://reliquary.redmage.cc/docs/how-to/invite-someone.md): Invite a person to a vault by email with a role, then send them the link yourself.
- [Set rules](https://reliquary.redmage.cc/docs/how-to/set-rules.md): Make a folder or file canon (changes need approval) or open (written directly), and choose how many people must approve.
- [Rotate a leaked token](https://reliquary.redmage.cc/docs/how-to/rotate-a-leaked-token.md): If an access token, a connection or a CLI sign-in may have leaked, revoke it, check what it did, and make a new one.

## Reference

- [MCP tools](https://reliquary.redmage.cc/docs/reference/mcp-tools.md): Every tool the Reliquary MCP server offers, with its arguments, limits and who may call it, generated from the server's own tool contract.
- [CLI](https://reliquary.redmage.cc/docs/reference/cli.md): Every `reliquary` command and option, with exit codes, environment variables and the project file.
- [Env API](https://reliquary.redmage.cc/docs/reference/env-api.md): The HTTP API the Reliquary CLI uses to read environment variables and send pushes, for anyone building their own client.
- [Permissions](https://reliquary.redmage.cc/docs/reference/permissions.md): What people and their agents can each do, where, and who may: every rule here is enforced by the database.
- [Limits](https://reliquary.redmage.cc/docs/reference/limits.md): The sizes, counts, rates and lifetimes Reliquary enforces, most of them in the database.
- [Errors and reference IDs](https://reliquary.redmage.cc/docs/reference/errors.md): When something fails, Reliquary tells you what it was doing, where it broke, why, and gives a reference ID. The web app, the MCP tools, the env API, OAuth and the CLI all say the same four things.
- [Glossary](https://reliquary.redmage.cc/docs/reference/glossary.md): The words Reliquary uses, each in one or two sentences, with a link to where it is explained.

## Optional

- [Roadmap](https://reliquary.redmage.cc/docs/roadmap.md): What Reliquary does today, what is being built, and what may come next.
- [Changelog](https://reliquary.redmage.cc/docs/changelog.md): What changed in each release of Reliquary, newest first.