MCP lets an agent discover and call Vision's tools. The agent host owns the conversation; Vision supplies authorized source operations, collected-record search, and runtime state.
Install Vision through Quickstart first. The examples here connect an existing installation; they do not select a new release or replace the public installation channel.
Connect Codex through the local plugin
A normal installation with setup scripts enabled prepares a local Codex marketplace inside that installed package's codex directory. Register the catalog for the actual installed package, then add its plugin:
codex plugin marketplace add "/absolute/path/to/the/installed/package/codex"
codex plugin add zortex@zortex-local
Use codex.cmd where required by your Windows shell. Do not guess the package directory from a different release's package name. Keep the referenced installation in place after registration.
If catalog preparation was skipped, or you need an explicit catalog tied to an existing Vault, create it:
indra setup codex --out "/absolute/path/to/a/new/catalog" --root "/absolute/path/to/your/Vault"
codex plugin marketplace add "/absolute/path/to/a/new/catalog"
codex plugin add zortex@zortex-local
Choose a new catalog directory; keep the Vault outside it. Check the generated binding points to the intended Vault and preserves your chosen environment settings. Creating a catalog does not itself sign in to accounts or prove MCP started.
Restart or reload the Codex session as required by that host. Its installed CLI and plugin interface determine when the new MCP server is loaded.
Verify the connection
- Confirm that the host lists the Vision
indra.*tools. - Read
indra.instructionwith{}. - Call
indra.managewith{"what":"onboarding"}. - Inspect one relevant source and run a small read or operation.
The first successful tool call establishes that the host can reach Vision. A completed source operation establishes that the selected connection works. These are separate checks.
When MCP starts, the product can start its automatic connection pass. Set your intended startup and sync controls before launching the host; see Permissions and source controls.
Use MCP manually
You can call tools without an agent through the official MCP Inspector. Check its current Node.js requirement; it can require a newer patch version than Vision's minimum.
Launch the Inspector with the installed Vision executable:
npx @modelcontextprotocol/inspector indra --root "/absolute/path/to/your/Vault" mcp
Follow the Inspector's printed local address and connection instructions. Connect to the configured standard-input/output server, open Tools, list the tools, and choose the operation to run. Enter the argument object from this reference and inspect the returned result.
Keep the terminal and the same Inspector connection alive through a multi-step operation. This is necessary for share.preview followed by share.create-link: previews belong to that running MCP context. Separate one-shot CLI calls cannot retain them.
Do not switch connections between preview and publication. If the process ends or the preview expires, inspect the current material and create a new preview. The Inspector is a manual MCP client; it does not supply an agent or automatically decide which operation to run.
Connect another local MCP host
Vision provides a standard-input/output server:
indra --root "/absolute/path/to/your/Vault" mcp
In a host's MCP configuration, select the actual installed executable and pass these arguments as separate entries:
["--root", "/absolute/path/to/your/Vault", "mcp"]
If the host cannot resolve indra, configure its absolute executable path. Hosts use different configuration formats; use the host's own command, arguments, and environment fields rather than pasting a guessed universal configuration file.
The host keeps the server process alive and communicates over standard input/output. Running this command interactively may wait silently for protocol messages. That is not an interactive chat terminal.
Refresh after a package update
For a supported installation whose existing catalog belongs to that exact package:
indra setup codex --refresh
Refresh preserves the confirmed Vault binding and relevant MCP environment. If it cannot confirm ownership, inspect the existing catalog instead of overwriting unrelated configuration. Restart the agent session after a successful refresh and verify a tool call.
Connect remotely
Use Remote access for a client running on another computer or in the cloud. Do not create a second Vault on that client to imitate access to the original computer.
If tools are absent, check the configured executable, catalog ownership, selected root, host logs, and whether the server is still running. If tools are present but a source fails, use connector recovery; reinstalling the MCP plugin does not repair an expired provider grant.