Loading workspace
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.
Most clients should use the streamable HTTP endpoint. You will be prompted to authenticate via OAuth and approve scopes.
Every client uses the same remote URL and discovers OrgX OAuth from the MCP domain. Do not paste an OrgX API key into any of these clients.
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.
In a supported workspace, enable developer mode, then open Workspace Settings → Apps → Create. Add the /mcp endpoint, choose OAuth, scan tools, and complete the sign-in prompt.
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"
}
}
}The exact UI differs by client, but the flow is always: add the server URL, authenticate, then run a first orchestration action.
Paste the streamable HTTP URL into your MCP client's "Add server" flow.
Complete OAuth in the browser and approve requested scopes. Scopes gate read/write tools.
Remember decisions, recall project context, review approvals, or track progress directly inside your client.
If you want a quick sanity check outside your client, hit the health endpoint.
curl -sS https://mcp.useorgx.com/healthzThe most common issues are transport selection, OAuth browser handoff, and stale auth sessions.
Choose streamable HTTP and set the URL to https://mcp.useorgx.com/mcp. Use SSE only if your client does not support streamable HTTP.
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.
The registry UI does not have per-server routes. Use the search URL: https://registry.modelcontextprotocol.io/?q=com.useorgx%2Forgx-mcp.
Open the MCP integration page, add the endpoint to your client, then complete OAuth and run your first orchestration command.