> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Client Setup

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

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.

> [!NOTE]
>
> 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

> [!TIP]
>
> An OrgX account at [useorgx.com](https://useorgx.com)

> [!TIP]
>
> Browser clients need an eligible account and OAuth support. No Node installation is required.

> [!TIP]
>
> Local Wizard setup requires Node.js 22 or newer; a local bridge has its own runtime requirements.

> [!TIP]
>
> A supported remote MCP client (ChatGPT, Cursor, Claude, VS Code, or
> equivalent)

## Quick Setup

> [tab] OpenClaw (Recommended)
>
> Install the plugin, then complete browser pairing:
>
> ```bash theme={"dark"}
> openclaw plugins install @useorgx/openclaw-plugin
> ```
>
> Then open the plugin dashboard, click **Connect OrgX**, and approve in your
> browser.
>
> [Full OpenClaw setup guide →](https://docs.useorgx.com/docs/guides/openclaw-plugin-setup.md)

> [tab] ChatGPT
>
> ### Step 1: Open OrgX in ChatGPT
>
> Open the
> [OrgX listing in the ChatGPT plugin directory](https://chatgpt.com/plugins/plugin_asdk_app_6a1083cac4788191a47b657dc58c4315),
> or search for **OrgX** under [Plugins](https://chatgpt.com/plugins).
>
> ### Step 2: Connect and authenticate
>
> Choose **Connect**. ChatGPT sends you through the OrgX OAuth flow
> in-browser. After that, you can use OrgX naturally in chat.
>
> > [!NOTE]
> >
> > No Developer Mode is needed. If your workspace blocks directory plugins,
> > add a Developer Mode connector with
> > `https://mcp.useorgx.com/mcp?profile=chatgpt` instead.
>
> > [!TIP]
> >
> > For ChatGPT-specific UX, widget examples, and permissions, see the
> > [ChatGPT integration guide](https://docs.useorgx.com/docs/guides/chatgpt-integration.md).

> [tab] Cursor IDE
>
> ### Step 1: Configure Cursor
>
> Edit your Cursor MCP configuration at `~/.cursor/mcp.json`:
>
> ```json theme={"dark"}
> {
>   "mcpServers": {
>     "orgx": {
>       "command": "npx",
>       "args": [
>         "mcp-remote",
>         "https://mcp.useorgx.com/mcp"
>       ]
>     }
>   }
> }
> ```
>
> ### Step 2: Restart Cursor
>
> Restart Cursor to load the MCP server. On first use, `mcp-remote` will open your browser for OAuth sign-in. Approve the connection and you're set.

> [tab] Claude
>
> ### Claude.ai or Claude Desktop custom connector
>
> On an individual Free, Pro, or Max plan, open **Customize → Connectors → +
> → Add custom connector** and use:
>
> ```text theme={"dark"}
> https://mcp.useorgx.com/mcp
> ```
>
> Or open the
> [prefilled OrgX connector form](https://claude.ai/customize/connectors?modal=add-custom-connector\&connectorName=OrgX\&connectorUrl=https%3A%2F%2Fmcp.useorgx.com%2Fmcp).
> On Team or Enterprise, an Owner or Primary Owner must first add OrgX under
> **Organization settings → Connectors → Add → Custom → Web**. Members then
> connect it from **Customize → Connectors**.
>
> Claude will open the OrgX OAuth flow in your browser.
>
> ### Claude Code direct MCP
>
> ```bash theme={"dark"}
> claude mcp add --transport http --scope user orgx https://mcp.useorgx.com/mcp
> claude mcp login orgx
> ```
>
> ### Claude Code public status plugin
>
> ```bash theme={"dark"}
> npx -y @useorgx/wizard@latest plugins add claude
> ```
>
> The public plugin provides static skills and commands plus
> native-OAuth MCP on the seven-tool, status-only `claude-directory` profile. It does not install transcript/context telemetry hooks or
> dynamic skill/agent sync.
>
> > [!NOTE]
> >
> > For hosted MCP, use Claude's Connectors UI or connect directly from
> > Claude Code. The public status plugin is a separate option for static
> > skills and commands.

> [tab] VS Code
>
> ### Step 1: Open VS Code MCP config
>
> Run **MCP: Open User Configuration** from the Command Palette.
>
> ### Step 2: Add OrgX
>
> ```json theme={"dark"}
> {
>   "servers": {
>     "orgx": {
>       "type": "http",
>       "url": "https://mcp.useorgx.com/mcp"
>     }
>   }
> }
> ```
>
> ### Step 3: Authenticate
>
> On first use, VS Code will launch the OrgX OAuth flow in your browser.

> [tab] Other MCP Clients
>
> If your client supports **remote MCP over HTTP/SSE + OAuth**, start with:
>
> ```text theme={"dark"}
> https://mcp.useorgx.com/mcp
> ```
>
> If the client asks for a specific transport route, use:
>
> * `https://mcp.useorgx.com/mcp` for streamable HTTP
> * `https://mcp.useorgx.com/sse` for SSE
>
> Use the SSE route only for clients that do not yet support streamable HTTP.

## Supported Clients At A Glance

| Surface | Setup style | Availability | Best for |
| - | - | - | - |
| ChatGPT | Plugin directory listing | Available | Conversational approvals + organizational memory |
| Cursor | `mcp-remote` + bare `/mcp` | Available | IDE-assisted coding + delivery |
| Claude custom connector | Connectors UI + bare `/mcp` | Available | Conversational planning + review |
| Claude Code direct MCP | `claude mcp add` + bare `/mcp` | Available | Terminal agent workflows |
| Claude Code self-hosted plugin | OrgX wizard | Available | Status and context reads; operating connector is separate |
| VS Code | HTTP server config + bare `/mcp` | Available | Planning and delivery inside editor |
| Other remote MCP clients | Root URL + OAuth | Varies | Generic MCP interoperability |

## Verify the selected profile

Follow [Product quickstart](https://docs.useorgx.com/docs/quickstart.md#2-confirm-a-useful-read): 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](https://docs.useorgx.com/docs/guides/onboarding.md#recovery).

## Widgets & Resources

OrgX MCP also exposes **resources** and **widgets**:

| Resource URI | Description |
| - | - |
| `orgx://initiative/{id}` | Full initiative details as markdown |
| `ui://widget/decisions.html` | Decision widget HTML |
| `ui://widget/agent-status.html` | Agent status widget HTML |
| `ui://widget/initiative-pulse.html` | Initiative pulse widget HTML |
| `ui://widget/morning-brief.html` | Morning brief widget HTML |

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:

| Transport | Endpoint | Use Case |
| - | - | - |
| **HTTP** | `https://mcp.useorgx.com/mcp` | Recommended streamable HTTP endpoint |
| **SSE** | `https://mcp.useorgx.com/sse` | Legacy SSE endpoint |

Both transports use the same OAuth 2.1 browser authorization flow when the
client supports remote MCP OAuth.

## Troubleshooting

> [accordion] Connection refused
>
> * 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`

> [accordion] Authentication failed
>
> * 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

> [accordion] Tools not appearing
>
> * Restart your IDE after updating `mcp.json` - Check the MCP config file for
>   JSON syntax errors - Run the health check command to verify connectivity

> [accordion] Permission denied on tool calls
>
> * 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

> [card] [MCP Protocol Reference](https://docs.useorgx.com/docs/api/mcp-protocol.md)
>
> Deep dive into the MCP protocol implementation.

> [card] [MCP Tools Reference](https://docs.useorgx.com/docs/api/mcp-tools.md)
>
> Complete API documentation for all tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.