Skip to main content
OrgX exposes a Model Context Protocol (MCP) server that integrates with ChatGPT, Cursor, Claude, VS Code, and other remote MCP clients. This gives agents shared organizational memory for decisions, artifacts, tasks, approvals, and project execution context without leaving the client you already use.
Use https://mcp.useorgx.com/mcp as the default hosted OrgX MCP URL. It is the streamable HTTP endpoint for remote MCP clients. ChatGPT is the exception: add OrgX from the ChatGPT plugin directory, or use https://mcp.useorgx.com/mcp?profile=chatgpt for a manual connector. Use https://mcp.useorgx.com/sse only when a legacy client explicitly asks for SSE.

Prerequisites

An OrgX account at useorgx.com
Browser clients need an eligible account and OAuth support. No Node installation is required.
Local Wizard setup requires Node.js 22 or newer; a local bridge has its own runtime requirements.
A supported remote MCP client (ChatGPT, Cursor, Claude, VS Code, or equivalent)

Quick Setup

Supported Clients At A Glance

Verify the selected profile

Follow Product quickstart: confirm the workspace and retrieve one linked record using tools actually discovered by your client. Use orgx_bootstrap only when present. The public Claude Code plugin uses claude-directory, which supports status and context reads and omits bootstrap and write tools. An empty workspace is a valid result. Choose an operating connector separately before creating work. A direct MCP connection, local runner installation, capture configuration, and delivered receipt are independent states. Doctor verifies local setup; the client verifies hosted OAuth. See connection recovery.

Widgets & Resources

OrgX MCP also exposes resources and widgets: Clients that support MCP Apps rendering can show OrgX decision, search, agent status, initiative pulse, task dispatch, and morning brief widgets inline.

Transport Options

The OrgX MCP server supports two transports: Both transports use the same OAuth 2.1 browser authorization flow when the client supports remote MCP OAuth.

Troubleshooting

  • Verify the MCP server URL is correct
  • Reconnect the MCP server entry in your client to refresh OAuth state
  • Ensure you have network access to mcp.useorgx.com
  • Disconnect and reconnect OrgX in your MCP client to restart OAuth - Complete browser sign-in and grant access to the correct workspace - Verify your OrgX account is active
  • Restart your IDE after updating mcp.json - Check the MCP config file for JSON syntax errors - Run the health check command to verify connectivity
  • Some tools require write scopes (for example, decision approvals)
  • Reconnect and approve broader scopes if prompted
  • Check that your OrgX role has the required permissions

Security Notes

  • OAuth access tokens are short-lived and refreshed by your MCP client
  • All traffic is encrypted via HTTPS
  • OAuth grants are scoped to specific permissions
  • Revoke access by disconnecting OrgX from your MCP client or OrgX settings

Next Steps

MCP Protocol Reference

Deep dive into the MCP protocol implementation.

MCP Tools Reference

Complete API documentation for all tools.