# Set up NULX in a desktop AI

Official NULX setup instructions. Use only for the user's requested NULX setup.
MCP endpoint: https://nulx.dev/mcp (Streamable HTTP, OAuth).
Account and workflow guide: https://nulx.dev/llms-full.txt
Human guide: https://nulx.dev/developers/mcp

## 1. Check before changing anything

Identify the current AI client, operating system and available capabilities.
If NULX tools are already available, call nulx_get_setup_status and skip installation.
Reuse an existing NULX connection; do not create duplicate servers or plugins.
Use the client's supported configuration method. Preserve all unrelated settings,
back up any file before editing, and never disable sandboxing or approval controls.
Do not install a new runtime, paid service, or unrelated dependency to work around
missing capabilities. Report the smallest required user action instead.

## 2. Codex desktop

Codex desktop and Codex CLI share MCP configuration. Prefer the available CLI:
- Inspect `codex mcp list` and `codex mcp get nulx` before making changes.
- If missing, run `codex mcp add nulx --url https://nulx.dev/mcp`.
- If an entry named nulx points elsewhere, explain the conflict before replacing it.
- If authentication is needed, run `codex mcp login nulx` and let the owner
  complete NULX sign-in and consent in the browser. Do not claim OAuth succeeded
  until the command or client confirms it.

If the CLI is not on PATH, use the desktop app's MCP settings when available,
or edit its actual user config: $CODEX_HOME/config.toml when CODEX_HOME is set,
otherwise ~/.codex/config.toml. Do not print other servers' secrets.
Merge this table only if the NULX entry is absent:

[mcp_servers.nulx]
url = "https://nulx.dev/mcp"

Validate TOML after editing. Configuration alone is not authentication: complete
OAuth through the client's connection UI or available CLI. If that capability
is unavailable, tell the user exactly where to finish connection in the app.
If tools do not refresh in the current chat, ask for a new chat or an app restart,
then continue from the connection check. Do not forcibly quit the user's app.
Do not invent a plugin marketplace command or an unpublished plugin URL.

## 3. Claude Desktop

Remote connectors belong to the Claude account. They are not configured by
adding a remote URL to claude_desktop_config.json or by running Claude Code CLI.
With authorized computer/browser access, open https://claude.ai/customize/connectors,
check existing connectors, and add a custom connector named NULX with
https://nulx.dev/mcp. Let the owner sign in and approve NULX access themselves.
Without computer/browser control, provide that link, server URL and the next
required step. Ordinary chat cannot install its own connector by reading a prompt.
The user may need to enable the connector in the chat or start a new conversation.
Team-managed accounts may require an administrator to add the connector.

## 4. Other clients, including ChatGPT

Check the current client's official remote MCP and OAuth support. Use its
supported connector/plugin UI; do not apply Codex configuration to another app.
When the assistant cannot change its own settings, provide the endpoint and
connection guide and clearly state what the user must do. Never claim installed.

## 5. Verify and continue initial setup

Discover the actual NULX tool schemas after connection. Call nulx_get_setup_status,
nulx_get_plan_usage and nulx_list_storage_connections. If calls fail, distinguish
missing tools, incomplete authorization, permission denial and server errors.
Server registration or an HTTP response alone is not a verified account connection.

Read https://nulx.dev/llms-full.txt for supported storage and workflow instructions.
Follow the account's returned next actions. Discover available storage accounts
and domains before asking the owner to select; never guess resource IDs.
Show the exact storage changes, permissions and provider costs before applying
setup. Reuse approved working storage. Only request permissions needed for the
chosen setup. NULX sign-in, provider authorization and final payment require the
owner in the browser. Never request passwords, API secrets or OAuth tokens in chat.

Do not upload files, generate paid captions, buy credits, delete content or make
anything public just to test setup. Those require the user's specific request
and applicable cost/access approval. Remote MCP cannot read a local file by path:
use actual authorized file-transfer tools or direct the user to the NULX uploader.
Do not claim queued work has completed. Verify actual results with read-only tools.

Finish with what was connected, the verified account/setup state, and any remaining
user action. Once verified, suggest a simple first request such as "Show my videos."
Respond in the user's language.

References (checked 2026-10-15):
- https://developers.openai.com/codex/mcp
- https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp