Skip to main content
OrgX connects to ChatGPT through an MCP connection. Use it when ChatGPT needs durable team memory, decision approvals, artifact recall, agent delegation, or project execution status.
Connect OrgX from ChatGPT Developer Mode. If Developer Mode is unavailable in your account or workspace, use Cursor, Claude, VS Code, or OpenClaw.

Features

Approve Decisions

Review and approve pending decisions when the connected ChatGPT client supports the OrgX decision widget.

Agent Status

See the current agent status exposed by the connected run surface.

Org Memory

Search your knowledge graph for context and history.

Spawn Tasks

Request new work from specialist agents once the connection is authenticated.

Getting Started

1

Enable Developer Mode

Open chatgpt.com/plugins. In Settings → Security, turn Developer Mode on.
2

Add the OrgX reviewer endpoint

In Developer Mode, choose +, add https://mcp.useorgx.com/mcp?profile=chatgpt, and save the private Developer Mode connection.
3

Authenticate

On first use, open the authentication link, sign in to OrgX, and grant ChatGPT permission to access the intended workspace.
OrgX uses OAuth 2.1 for this connection. Review both OrgX’s and the connected provider’s current data-handling terms.
4

Start Using

Once connected, just talk to ChatGPT naturally:
  • “Show me pending decisions”
  • “What are my agents working on?”
  • “Approve the marketing campaign decision”
  • “Search for our pricing strategy decisions”
  • “Remember this decision for the team: we are moving onboarding analytics to PostHog.”

Available Commands

Tier-0 Intent Tools

Start with these wrapper tools. They map to the natural phrases ChatGPT users actually type while preserving the underlying OrgX behavior.

Decision Management

What it does: Retrieves all decisions waiting for your approval.Example prompts:
  • “Show my pending decisions”
  • “What needs my approval?”
  • “Any critical decisions waiting?”
Parameters:
  • limit (optional): Maximum number to return
  • urgency_filter (optional): all, critical, or high
  • initiative_id (optional): Filter by specific initiative
Response: The client may render decision cards; response fields depend on the connected surface.
What it does: Records approval for a pending decision. A configured follow-on action may then become eligible or be dispatched; approval alone is not proof of an external result.Example prompts:
  • “Approve the homepage redesign decision”
  • “Approve decision [decision_id] with note: approved after review”
Parameters:
  • decision_id (required): ID of the decision
  • note (optional): Comment to attach
Response: The client returns the fields available for the recorded decision. Inspect the record and any downstream provider receipt separately.
What it does: Rejects a decision with feedback for the agent.Example prompts:
  • “Reject the email campaign, needs more personalization”
  • “Reject decision [decision_id] because the budget is too high”
Parameters:
  • decision_id (required): ID of the decision
  • reason (required): Why you’re rejecting
Response: The client returns the fields available for the recorded decision. A configured workflow may route the feedback for revision.
What it does: Retrieves past decisions on a topic.Example prompts:
  • “What decisions have we made about pricing?”
  • “Show me past marketing decisions”
Parameters:
  • topic (required): What to search for
  • initiative_id (optional): Filter by initiative
  • limit (optional): Maximum results

Agent Management

What it does: Shows current agent activity and status.Example prompts:
  • “What are my agents doing?”
  • “Show me active agents”
  • “Is the engineering agent working on anything?”
Parameters:
  • agent_id (optional): Filter to specific agent
  • include_idle (optional): Show idle agents too
Response: The client may render agent cards with the current fields returned by the connected run surface.
What it does: Assigns a new task to a specialist agent.Example prompts:
  • “Have the product agent analyze our competitor positioning”
  • “Ask the marketing agent to draft a blog post about our new feature”
Parameters:
  • agent (required): Canonical agent ID (engineering-agent, product-agent, marketing-agent, sales-agent, design-agent, operations-agent, orchestrator-agent)
  • task (required): What to do
  • context (optional): Additional background
  • initiative_id (optional): Link to an initiative
Response: The client returns the accepted, blocked, or recorded state available for the delegation request. Do not infer completion from dispatch.
This writes to your workspace. A connection that is authenticated can call it — the agents:write scope is recorded at consent time but is not checked on the call. Authorize ChatGPT from an account whose workspace membership matches the writes you want it to be able to make.
What it does: Searches your organizational knowledge graph.Example prompts:
  • “What do we know about enterprise pricing?”
  • “Find artifacts related to [initiative_or_topic]”
  • “Search for previous security audits”
Parameters:
  • query (required): What to search for
  • scope (optional): all, artifacts, decisions, or initiatives
  • limit (optional): Maximum results
Response: The client may render relevant items with excerpts and links.
What it does: Shows health and progress of an initiative.Example prompts:
  • “How is the product launch initiative doing?”
  • “Show me the pulse for initiative [initiative_id]”
Parameters:
  • initiative_id (required): Which initiative to check
Response: The client may render the initiative fields returned by the connected OrgX surface.

Widgets

When the connected ChatGPT surface supports them, OrgX can use rich widgets to display information rather than plain text:

Decisions Widget

Interactive cards with approve/reject buttons, context, and evidence links.

Agent Status Widget

Visual cards showing each agent’s current task, progress, and health.

Search Results Widget

Organized results with type icons, excerpts, and deep links.

Initiative Pulse Widget

Dashboard view with health score, milestone progress, and activity feed.

Permissions & Security

Scopes

The consent screen lists the scopes the connection declares. They describe intent and appear back in the orgx_bootstrap payload as granted_scopes.
Scopes are consent and discovery metadata, not a privilege boundary. OrgX does not compare a tool call against the scopes you granted. What is enforced is authentication — an OAuth-declaring tool is refused without a signed-in user — and workspace membership, which decides which records that user can reach. Approving fewer scopes does not make the connection read-only. Connect ChatGPT from an account whose workspace access you are willing to give it, and see Declared scopes for the mechanism.
The authenticated ChatGPT reviewer endpoint is https://mcp.useorgx.com/mcp?profile=chatgpt and requires OrgX OAuth. For no-auth exploration, use the discovery-only public endpoint at https://mcp.useorgx.com/public; it returns examples and connection help, not workspace data.

Data Privacy

  • Your messages in ChatGPT are processed by OpenAI per their policies
  • OrgX receives the MCP requests and responses required by the connection, not an implied copy of the entire ChatGPT conversation
  • All API calls are authenticated and scoped to your workspace
  • Data handling and retention follow the current OrgX privacy policy and the connected provider’s policy; this page does not promise zero retention

Troubleshooting

  1. Verify Settings -> Security -> Developer Mode is enabled
  2. Confirm you’ve added https://mcp.useorgx.com/mcp?profile=chatgpt
  3. Restart ChatGPT if the connection does not appear
  1. Try clearing your browser cache and re-authenticating 2. Make sure you’re signing into the correct OrgX workspace 3. Check that your OrgX account is in good standing
  • Ensure you have pending decisions in your OrgX workspace - Confirm the connection is signed in and pointed at the workspace that holds them - Try refreshing by asking “Show pending decisions” again
Write operations require a signed-in connection whose account can act in that workspace. Re-authenticate, and confirm the account you signed in with is a member of the workspace holding the decision.

Next Steps

MCP Client Setup

Connect OrgX from Cursor, Claude, VS Code, and other MCP clients.

MCP Tools Reference

Current reference for the published MCP tools.