OrgX MCP config for every client
One hosted endpoint, browser sign-in, no API key. Pick your client, copy the config, then ask the agent to call orgx_get_workspace_context to confirm the workspace.
https://mcp.useorgx.com/mcp- Claude CodeAdd OrgX to Claude Code with two commands and browser OAuth.Remote HTTP
- Claude (desktop and web)Connect OrgX to Claude as a custom connector with one URL.Remote HTTP
- CursorAdd OrgX to ~/.cursor/mcp.json through mcp-remote.stdio via mcp-remote
- VS CodeAdd OrgX as an HTTP server in the VS Code MCP user configuration.Remote HTTP
- Codex CLIAdd OrgX to ~/.codex/config.toml and sign in with codex mcp login.Remote HTTP
- ChatGPTConnect OrgX from the ChatGPT plugin directory: find OrgX, connect, and approve your workspace.Remote HTTP
- OpenClawInstall the OrgX plugin for OpenClaw and pair it in the browser.Local bridge
Questions
- What is the OrgX MCP server URL?
- https://mcp.useorgx.com/mcp. It uses streamable HTTP with OAuth 2.1 and PKCE. In ChatGPT, add OrgX from the ChatGPT plugin directory; a manual Developer Mode connector uses https://mcp.useorgx.com/mcp?profile=chatgpt.
- Is OrgX available in ChatGPT?
- Yes. OrgX is listed in the ChatGPT plugin directory at https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315. Open the listing or search for OrgX under Plugins in ChatGPT, choose Connect, and approve your workspace. No Developer Mode is needed.
- Do I need an API key to connect OrgX over MCP?
- No. Your client opens OrgX in a browser, you sign in, and you choose the workspace and access to grant.
- How do I check the connection worked?
- Ask the agent to call orgx_get_workspace_context. The result should show the workspace you expected and the capabilities your workflow needs.
- My client cannot use streamable HTTP. What now?
- Use the legacy SSE endpoint at https://mcp.useorgx.com/sse, or bridge with npx mcp-remote as the Cursor config does.