GUIDE

Connect OrgX MCP for One Shared Record

Add OrgX to any MCP-compatible client so agents can remember decisions, recall artifacts, approve work, delegate tasks, and track project progress without context switching.

MCP integration page Docs home MCP Registry

TLDR

Use streamable HTTP + OAuth

Most clients should use the streamable HTTP endpoint. You will be prompted to authenticate via OAuth and approve scopes.

Streamable HTTP (recommended)

https://mcp.useorgx.com/mcp

SSE (legacy)

https://mcp.useorgx.com/sse

Client-specific configuration

Each client uses its documented profile URL and discovers OrgX OAuth from the MCP domain. Do not paste an OrgX API key into any of these clients.

CLAUDE

Add a custom connector

Open Settings → Connectors. For a Team or Enterprise organization, choose Organization connectors. Add a custom connector, paste the /mcp URL, then select Connect and finish OAuth.

CHATGPT

Add OrgX from the ChatGPT plugin directory

Open the OrgX listing in ChatGPT, choose Connect, and approve your workspace with OrgX OAuth. If your workspace blocks directory plugins, add https://mcp.useorgx.com/mcp?profile=chatgpt as a Developer Mode connector.

CURSOR

Add a remote MCP server

Save this globally in ~/.cursor/mcp.json or per project in .cursor/mcp.json. Then open Tools & MCP, choose OrgX, and complete OAuth.

{
  "mcpServers": {
    "orgx": {
      "url": "https://mcp.useorgx.com/mcp"
    }
  }
}

Step-by-step setup

The exact UI differs by client, but the flow is always: add the server URL, authenticate, then run a first orchestration action.

Add endpoint

Paste the streamable HTTP URL into your MCP client's "Add server" flow.

OAuth sign-in

Complete OAuth in the browser and approve requested scopes. Scopes gate read/write tools.

Use shared memory

Remember decisions, recall project context, review approvals, or track progress directly inside your client.

Verify it's live

If you want a quick sanity check outside your client, hit the health endpoint.

curl -sS https://mcp.useorgx.com/healthz

If this returns 200, the server is reachable. If your client still cannot connect, it is usually an OAuth pop-up / browser-hand-off issue.

Troubleshooting

The most common issues are transport selection, OAuth browser handoff, and stale auth sessions.

Client asks for a transport type

Choose streamable HTTP and set the URL to https://mcp.useorgx.com/mcp. Use SSE only if your client does not support streamable HTTP.

OAuth sign-in doesn't complete

Make sure your client can open a browser window and handle the callback. If needed, remove the connection and re-add it to restart the PKCE flow.

MCP Registry link 404s

The registry UI does not have per-server routes. Use the search URL: https://registry.modelcontextprotocol.io/?q=com.useorgx%2Forgx-mcp.

Ready to connect?

Open the MCP integration page, add the endpoint to your client, then complete OAuth and run your first orchestration command.

MCP integration page Docs home