Connect your toolsOrgX MCP
One URL connects every MCP client.
Each AI client keeps its own memory, so what one learns the others never see. The OrgX MCP server lets any client read what is decided, ask for decisions, and write back what it did.
Switch the client. The next session opens with the same rules, skill and decision.
Starting: adding turbo.
OrgX · loaded 3 things already decided
- Use pnpm in northstar/web; npm breaks the lockfileRule
- Add a dependency in northstar/webSkill
- Launch copy leads with the agency buyerDecision, by Priya
Criteria set before work started · 3
- Uses pnpm, not npmFrom the team’s rule
- Follows “Add a dependency in northstar/web”Skill from 4 runs that passed CI
- Judged on 5 layersYour standard
- pnpm add the package
- Run pnpm build
- Commit pnpm-lock.yaml only
Receipt · 3 of 3 criteria met · ready to approve
- Ran in
- Claude Code
- Steps
- 3, listed above
- Uses pnpm, not npm
- Passed on the commands this run used
- Follows “Add a dependency in northstar/web”
- 3 of 3 steps done
- Judged on 5 layers
- Each layer above the bar
Also inOpenClawOpenCodeAny MCP client
One command finds Claude Code, Codex and Cursor on this machine and connects each one.
npx -y @useorgx/wizard@latest setupDesktop terminal, Node.js 22+. Review the changes it proposes, then sign in.
Setup guide- Any MCP clientOne server URL, sign in once, works wherever MCP does.
- Read what is decidedRules, skills and decisions for the task, before the agent starts.
- Write back what happenedDecisions asked, work done and proof attached, from the client itself.
How it works
- Add the server URL to your client.
- Sign in and choose a workspace.
- Every session reads and writes the same record.