TARX

ChatGPT forgets. TARX remembers.

Private, local-first memory for ChatGPT, and only when you approve it.

Connect ChatGPT to https://mcp.tarx.com/mcp. Use public TARX context before linking an account. Link TARX when you want private memory that lives in TARX, not ChatGPT memory. Passwords, API keys, and raw credentials belong in TARX local vault workflows, not chat memory.

Current launch truth: public TARX context is live now, and private memory now uses normal TARX sign-in rather than pasted keys or internal secrets. The ChatGPT-facing tool surface is six tools, tuned for context, memory, and secure workflows.

Core claim: Give ChatGPT private memory you control.

Canonical scope: TARX

ChatGPT tools: search, fetch, tarx_status, tarx_context, tarx_memory_search, tarx_memory_store

Private memory: tarx_memory_search, tarx_memory_store

How it works

Connect ChatGPT to https://mcp.tarx.com/mcp.
Use search and fetch before account linking.
Use normal TARX sign-in to unlock private memory for your TARX account.
Store user-approved memories in TARX, scoped to the connected account.
Push passwords, keys, and raw credentials into TARX local vault workflows instead of memory.

Privacy ladder

Public context: docs, install help, product facts.
Private memory: preferences, decisions, meeting notes, GTM context.
Local vault workflows: passwords, API keys, tokens, SSH keys, private keys, raw credentials.

What TARX does not do

No Vault access from ChatGPT.
No raw local filesystem browsing from ChatGPT.
No background sync of full ChatGPT history.
No autonomous task execution before the memory connector is trusted.

Anonymous access only returns product docs and install guidance. Private memory unlocks only after TARX account approval for this ChatGPT connection.

Canonical private-workflow spec: https://mcp.tarx.com/openai-context/tarx%3Aprivate-workflows

OpenAI function tools export: https://mcp.tarx.com/openai-tools