Connect Context to your AI

1. Account and personal token

Create an account. Give the connection a name you will recognize and issue a token. This secret key lets your AI tool access Context. Its full value is shown only once: save it immediately in protected storage. If you close or hide it, check your connection list first.

2. Choose a connection method

Use only the authenticated account MCP connection below. Context reads the public library. Keep personal and project documents in your AI host chat or workspace. Never put personal information, secrets, or private project content in public profile name, scope, or topics. The host controls conversation memory; MCP cannot guarantee its isolation or deletion.

https://startzorya.com/mcp/context-account

The free beta includes all 13 Context tools: the catalog, knowledge selection and preparation, research, personal knowledge sessions and export. Research and exports require separate consent. Document import is unavailable in the account MCP. Model and external-service charges are separate. Large context uses more input tokens, so start with a lightweight compatible model and one small question.

Enter the Bearer token in the MCP client’s protected authorization settings; public mcp.json contains no credentials and does not configure them for the client. The server alias is zorya_context_account. The package version is sent in X-Zorya-Context-Client-Version. For Codex CLI use codex mcp add zorya_context_account --url https://startzorya.com/mcp/context-account --bearer-token-env-var ZORYA_CONTEXT_TOKEN. In Cursor, set the version header statically and Authorization through a protected environment variable.

codex mcp add zorya_context_account --url https://startzorya.com/mcp/context-account --bearer-token-env-var ZORYA_CONTEXT_TOKEN

{
  "mcpServers": {
    "zorya_context_account": {
      "url": "https://startzorya.com/mcp/context-account",
      "headers": {
        "Authorization": "Bearer ${env:ZORYA_CONTEXT_TOKEN}",
        "X-Zorya-Context-Client-Version": "0.3.4"
      }
    }
  }
}

read -r -s -p "Zorya Context token: " ZORYA_CONTEXT_TOKEN
export ZORYA_CONTEXT_TOKEN
printf '\n'

Run these commands in the same terminal from which you start the client. read -s hides the token while you type; the token value is not written in the command. After starting the client, run unset ZORYA_CONTEXT_TOKEN when you no longer need the variable.

An environment variable is available only to processes that inherit it when they start. A terminal, an app launched from the desktop menu, an SSH session, WSL, and a remote client may have different environments. Set the variable in the environment of the process that opens the MCP connection, then restart that process; a value set in a local terminal is not automatically available to a desktop app, SSH, WSL, or remote environment.

Start with a short request

Open the guide and choose one small example. This lets you check the connection and judge the result before trying a longer workflow.

Three more useful prompts

Use catalog and read to find material about API compatibility. Review my plan: which clients may depend on the old contract? Separate supported facts from assumptions; name sources and gaps. Do not start research or change code.

Find relevant saved knowledge and compare the two approaches I describe. State versions, applicability, tradeoffs, sources, and unknowns. Do not start new research.

First check the catalog and read relevant items. If an important gap remains, say whether research is available in this configuration. If it is, propose a goal, benefit, and duration up to 600 seconds. Do not start without my separate explicit consent.

Project instruction updates (optional)

During setup, ask the project owner whether to enable startup checks. Existing clients need a one-time reviewed setup: install the five signed files in .agents/skills/context-account/, the updater at .codex/zorya-context/update.mjs, the version marker in .codex/config.toml, and bootstrap it. An old client cannot run an updater it does not have. Public MCP configuration contains the server URL and package version, not a token or automatic credential setup; configure Bearer in the client’s protected settings.

1. Download the current zorya-context-account-beta.tar.gz package and review its contents. Do not enable project startup checks if you do not want automatic instruction updates.
2. Copy README.ru.md, mcp.json, plugin.json, and release.json to .agents/skills/context-account/; copy skills/context-account/SKILL.md as .agents/skills/context-account/SKILL.md. Copy scripts/update.mjs to .codex/zorya-context/update.mjs.
3. In .codex/config.toml, preserve the existing protected Bearer configuration. Under [mcp_servers.zorya_context_account.http_headers], add a separate managed version marker using the version in the installed release.json (for example 0.3.4) in the exact template format.
4. From the project root, run node .codex/zorya-context/update.mjs --bootstrap once. After it confirms the verified current version, manually add the startup block from this guide to AGENTS.md, preserving its existing rules. Later, run --check-and-update before other work in this project.
5. For a portable package copy, keep the signed files in the archive layout and run node scripts/update.mjs --bootstrap once from the package root; use the same command with --check-and-update for later checks.

For a portable package copy, preserve the archive layout and run node scripts/update.mjs --bootstrap once from its root. Later project checks use node .codex/zorya-context/update.mjs --check-and-update; portable checks use node scripts/update.mjs --check-and-update.

The updater verifies the bounded release at https://startzorya.com/assets/zorya-context-client-release.json using its pinned Ed25519 signature and hashes. In project mode it changes the five signed files and managed version marker in .codex/config.toml; unknown files are preserved. Managed-file edits and signature/hash errors stop the update. Offline, keep the last verified version and report the failed check. The updater bootstrap itself needs separate manual review.

[mcp_servers.zorya_context_account.http_headers]
# BEGIN ZORYA CONTEXT CLIENT VERSION
"X-Zorya-Context-Client-Version" = "0.3.4"
# END ZORYA CONTEXT CLIENT VERSION

## Zorya Context trusted startup updates

This project owner has enabled the installed Zorya Context updater. Before dependent work, immediately run `node .codex/zorya-context/update.mjs --check-and-update` without another confirmation. Keep success silent; report only failures or required user action. It verifies the bounded release at `https://startzorya.com/assets/zorya-context-client-release.json` with the pinned Ed25519 key and hashes. It updates only the five signed files under `.agents/skills/context-account/` (`plugin.json`, `mcp.json`, `release.json`, `README.ru.md`, `SKILL.md`) and the managed version-header block in `.codex/config.toml`. Preserve unknown files and all existing project instructions. It never changes Bearer tokens, private/global settings, or application code. Stop on edits to managed files or signature/hash errors. If offline, keep the last verified version and report that the check did not complete. Updating the updater bootstrap itself requires manual review. After actual managed-file changes, reread the installed skill and refresh cached MCP schemas or reconnect. If the verified local package is current but the connection reports an old or unknown version, reconnect once and report a persistent mismatch instead of looping.

Updates

Server-side MCP tools update centrally. If the owner already enabled an installed trusted updater, the agent runs its check immediately before dependent work, without another confirmation. Success stays silent; report only failures, missing setup or required action. After actual file changes, reread the skill and refresh cached schemas or reconnect. If the local verified version is current but the connection reports an old or unknown version, reconnect once; report a persistent mismatch instead of looping updates. Without configured updates, never install a bootstrap or change settings automatically. The server cannot change host files itself or guarantee compliance with this instruction.

• The account MCP provides 13 tools without document import.
• Research, export, jobs, and KnowledgeSession remain available.
• Instructions clarify public profiles and host conversation memory.

Package version 0.3.4. X-Zorya-Context-Client-Version identifies the package but does not replace acceptedBundleFormats: [1, 2]. Set that field only on supported new-request schemas; preserve returned next unchanged. Correct a confirmed rejected or not-accepted request only within its original consent and remaining time, without resetting the deadline; resolve an uncertain submission by exact retry first. A stale schema requires the trusted update and reconnect. Client updates cannot enable server-disabled collection; available V1 knowledge remains reusable.

Troubleshooting