Questions This Page Answers
- Which endpoint should I use for hosted OrgX MCP vs local OpenClaw bridge?
- How does OAuth work in practice for MCP clients?
- What scopes should I request for decisions, dispatch, and memory workflows?
- How do I avoid confusing the hosted OrgX tool surface with plugin-local tools?
What is MCP?
The Model Context Protocol is an open standard for connecting AI assistants to external tools and data. It enables:- Tools: Actions the AI can take (approve decisions, spawn tasks)
- Resources: Data the AI can access (initiatives, artifacts)
- Prompts: Pre-built conversation templates
Connecting to OrgX
Hosted MCP vs OpenClaw Local Bridge
OrgX supports two MCP connection modes:
The hosted server and plugin bridge expose overlapping tools, but they are not identical surfaces.
Use the OrgX MCP Tools Reference for hosted tools and OpenClaw Plugin Tools for local bridge tools.
Server Endpoints
Use
https://mcp.useorgx.com/mcp for new clients. Use the SSE endpoint only
when a legacy client cannot speak streamable HTTP.Authentication
OrgX MCP uses OAuth 2.1 with browser-based authorization. Remote MCP clients that support OAuth handle sign-in automatically. How it works:- Your MCP client discovers the auth server via RFC 9728 metadata at
/.well-known/oauth-protected-resource - You’re redirected to sign in at useorgx.com via Clerk
- After approving the connection, the client receives and manages tokens automatically
- Token refresh is handled transparently by the client
authorization_code, refresh_token
PKCE support: S256, plain
Available Scopes
Request the scopes you need when authenticating:Quick Setup
- OpenClaw (Recommended)
- Cursor
- Claude
- VS Code
The fastest setup — handles auth automatically:Then open
http://127.0.0.1:18789/orgx/live, click Connect OrgX, and approve in your browser.Full OpenClaw guide →Supported Client Patterns
Protocol Capabilities
OrgX MCP tools are organized by user intent. Start with the Tier-0 tools for tool routing, then use the lower-level tools when you need exact control.Tier-0 Entry Points
orgx_decide- Save a decision to organizational memoryorgx_search- Search decisions, artifacts, and project contextorgx_decide- Review pending approvals and approve/reject after confirmationorgx_spawn- Assign work to a specialist AI agentorgx_recommend- Get initiative health, blockers, milestones, owners, and activity
Execution
orgx_spawn- High-recall wrapper for assigning work to an agentorgx_spawn- Assign work to a specialized agent (Engineering, Marketing, Product, etc.)orgx_act- Trigger lifecycle actions on any entity (start, complete, block, etc.)scaffold_initiative- Create a full initiative hierarchy in one callbatch_create_entities- Bulk-create tasks, milestones, or workstreams in a single operation
Decisions
orgx_decide- High-recall wrapper for pending approval revieworgx_search- Filtertype=decisionandstatus=pendingto list decisions awaiting approvalorgx_decide- Approve a decisionorgx_decide- Reject with feedback
Memory & Context
orgx_decide- Record a decision so agents can recall it laterorgx_search- High-recall wrapper for organizational memory searchorgx_search- Search organizational knowledge and past decisionsorgx_recommend- High-recall wrapper for project status and blockersorgx_recommend- Get initiative health status and execution signalsorgx_recommend- Retrieve a full org-level summary for grounding agent context
Planning
orgx_plan- Open an interactive planning session for an initiative or workstreamorgx_plan- Apply structured improvements to an existing planorgx_plan- Finalize and commit a plan, making it actionable
Legacy aliases such as
orgx_decide and get_decision_history
still resolve for older clients. For new natural-language client routing,
prefer the Tier-0 tools above first, then drop down to orgx_search,
orgx_search, and the direct write tools when needed.Resources
The MCP server also exposes resources for rich context:Troubleshooting
Connection refused
Connection refused
- Verify the endpoint URL matches your mode (hosted vs local bridge).
- Hosted: ensure network access to
mcp.useorgx.com. - Local bridge: ensure OpenClaw gateway is running and
http://127.0.0.1:18789/orgx/liveis reachable.
Authentication failed
Authentication failed
- Hosted OAuth: reconnect from your MCP client and complete browser sign-in
again. - OpenClaw bridge: reconnect in plugin onboarding or re-enter a fresh
oxk_...key. - Confirm your OrgX account has access to the target workspace.
Tools not appearing
Tools not appearing
- Restart your IDE after updating config
- Check MCP config syntax (
mcpServersentry and endpoint URL). - If using OpenClaw, verify bridge health at
/orgx/api/healthand onboarding status at/orgx/api/onboarding/status.
Next Steps
MCP Tools Reference
Complete documentation for all tools.
OpenClaw Plugin Tools
Local bridge tools and scoped domain matrix.
MCP Client Setup
Client-by-client setup for ChatGPT, Cursor, Claude, VS Code, and more.
