Skip to main content
Start here. The AI Toolkit is the single entry point for connecting OrgX to the AI clients you already use. The wizard configures supported local clients; ChatGPT Developer Mode and provider directories use separate setup and review flows.

Connect Organizational Memory to Your AI Tools

OrgX gives Claude, Cursor, Codex, VS Code, Windsurf, Zed, ChatGPT, Gemini CLI, and other MCP clients shared organizational memory: decisions, artifacts, tasks, approvals, and project execution context. Choose the supported setup path for each client.

3 Ways to Connect

Path A: Wizard CLI

Recommended. Detects which AI clients you have installed and configures them automatically.
Handles OAuth, config files, and auto-update for supported local clients. It does not submit or publish OrgX in OpenAI or Anthropic directories.

Path B: Skills

Manual. Add OrgX directly via your client’s skill or plugin interface.Best for clients with a built-in plugin marketplace (OpenClaw, VS Code extensions).See OpenClaw Plugin Setup →

Path C: MCP Direct

Raw endpoint. Point any MCP-compatible client at the hosted server.
Handles OAuth automatically on first connect. See MCP Protocol →

Client Compatibility Matrix


What the Toolkit Includes

Wizard CLI

Auto-configure supported local clients. npx @useorgx/wizard@latest setup detects Claude, Cursor, VS Code, Codex, Windsurf, and Zed, then writes supported config files and keeps them in sync. Hosted directory review flows remain separate.

Hosted MCP Server

Organizational memory + execution control. https://mcp.useorgx.com/mcp is the general OAuth-protected streamable HTTP endpoint. Reviewed clients can use focused profiles; ChatGPT Developer Mode uses ?profile=chatgpt. Provider directory listings are separate from endpoint availability.

Skills & Plugins

Native integration. The OpenClaw plugin wires OrgX into the local AI runtime with browser-pairing in 60 seconds. Skills inject OrgX context directly into agent instruction sets.

Live Dashboard

Mission Control. Every decision, artifact, and initiative is visible in the web app — and actions taken in any client (Claude, Cursor, ChatGPT) surface here in real time.

Explore Before Full Setup

Use these paths before wiring a full production workspace:

Sandbox Playground

Visit useorgx.com/playground after signing in to try guided sandbox flows without configuring an external MCP client.

Public MCP Endpoint

Connect any MCP client to https://mcp.useorgx.com/public for no-auth discovery tools, example payloads, and connection help. It does not expose workspace data or execute authenticated OrgX actions.
To add the public endpoint to Cursor (or any client that supports mcp-remote), add this to your MCP config:
The public endpoint is discovery-only. To remember decisions, search real workspace memory, approve work, or spawn agents, connect the authenticated MCP endpoint at https://mcp.useorgx.com/mcp.

Next Steps

Wizard CLI Onboarding

Complete walkthrough for the fastest setup path.

Cursor + MCP Setup

Manual Cursor configuration if you prefer not to use the wizard.

ChatGPT Integration

Add the private Developer Mode endpoint and check the separate directory publication state.

OpenClaw Plugin Setup

60-second browser pairing for local OpenClaw runtimes.

Agent Quickstart

Spawn your first agent task once you’re connected.