OrgX MCP — organizational continuity for AI agents

The task outlives the chat. OrgX MCP is organizational continuity for AI agents. Make AI work resumable, reviewable, and provable across agents. OrgX lets the next agent continue from the decisions, artifacts, approvals, owners, and proof the last agent left behind.

How: organizational memory. OrgX MCP lets agents remember decisions, recall artifacts, review pending approvals, assign work to specialist agents, track initiative health, and render interactive workflows in MCP Apps-compatible clients.

Try these prompts

Continue what the other agent started on the onboarding analytics migration.

What did we decide about billing, and why?

Who approved this?

Show me it actually shipped.

Remember this decision for the team: we are moving onboarding analytics to PostHog.

Assign this research task to an agent and tell me when it's done.

What is blocked on the Growth Launch initiative?

Install

Verified onboarding paths — the setup wizard:

npx -y @useorgx/wizard setup

or connect the remote MCP URL:

https://mcp.useorgx.com/mcp

Use the Memory profile when you want OrgX to act as shared organizational memory for Claude, ChatGPT, Cursor, and AI agents. Use the Full profile when you want planning, task delegation, widgets, and initiative execution.

What OrgX MCP Does

OrgX MCP is organizational continuity for AI agents. Make AI work resumable, reviewable, and provable across agents. It connects Claude, ChatGPT, Cursor, and other MCP-capable clients to OrgX so users can:

• review pending decisions and approvals,
• inspect agent activity and initiative health,
• query organizational memory,
• scaffold initiative hierarchies,
• assign work to OrgX agents,
• render OrgX widgets in MCP Apps-compatible hosts.

Practical founder and team artifacts

OrgX agents should return the next useful company artifact for the user's stage, not generic analysis. For an early founder, that may be a sales strategy, customer discovery synthesis, pricing hypothesis, launch asset, or first PR. For an existing founder-led company or operating team, it may be a weekly operator brief, roadmap decision, reliability fix, budget envelope, or cross-domain initiative with owners and acceptance gates.

Normal agent work should let OrgX auto-route by task complexity and workspace policy. Use explicit low-cost routing only for controlled reliability validation or when the user/workspace sets a budget constraint.

Tools (v2 public surface — see server.json for the full contract)

Tool	Purpose
orgx_bootstrap	Establish session context, scopes, and routing guidance.
orgx_search	Find entities, decisions, artifacts, and memory.
orgx_inspect	Hydrate one entity with execution context.
orgx_recommend	Get next-action recommendations or morning brief signals.
orgx_write	Create or update durable OrgX records.
orgx_attach	Attach proof, URLs, documents, screenshots, or artifacts.
orgx_act	Launch, pause, complete, validate, delete, or otherwise act on an entity.
orgx_plan	Start, resume, edit, improve, or complete a plan session.
orgx_spawn	Guard, classify, spawn, or hand off specialist agent work.
orgx_decide	Create, remember, approve, reject, or list decisions.
orgx_submit_receipt	Submit durable proof, attribution, quality, or outcome receipts.
orgx_emit_activity	Emit append-only execution telemetry.
orgx_request_attention	Forward a typed question, permission, approval, or recovery request with native continuation context.
orgx_poll_attention	Read the durable answer and client continuation state.
orgx_ack_attention	Confirm that the source client received, resumed, failed, or cancelled continuation.
orgx_request_question