Agent orchestration + org memory via MCP. Manage initiatives and decisions from any client.
If you already use OrgX MCP, the orgx mcp mcp server is the piece that lets your assistant work with it directly. Agent orchestration + org memory via MCP. Manage initiatives and decisions from any client.
The task outlives the chat. OrgX MCP is organizational continuity for AI agents. Make AI work resumable, reviewable, and provable across agents. OrgX lets the next agent continue from the decisions, artifacts, approvals, owners, and proof the last agent left behind.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
orgx_bootstrap — Establish session context, scopes, and routing guidanceorgx_search — Find entities, decisions, artifacts, and memoryorgx_inspect — Hydrate one entity with execution contextorgx_recommend — Get next-action recommendations or morning brief signalsorgx_write — Create or update durable OrgX recordsorgx_attach — Attach proof, URLs, documents, screenshots, or artifactsorgx_act — Launch, pause, complete, validate, delete, or otherwise act on an entityorgx_plan — Start, resume, edit, improve, or complete a plan sessionorgx_spawn — Guard, classify, spawn, or hand off specialist agent workorgx_decide — Create, remember, approve, reject, or list decisionsorgx_submit_receipt — Submit durable proof, attribution, quality, or outcome receiptsorgx_emit_activity — Emit append-only execution telemetryConfiguration is passed through the environment: MCP_SERVICE_KEY, ORGX_SERVICE_KEY, ORGX_API_URL, MCP_JWT_SECRET, ORGX_INTERNAL_SECRET, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
pnpm (matches the repo's package manager) - Cloudflare account with Workers enabled - The following environment variables must be configured for both the worker and the Next.js app: - MCP_SERVICE_KEY (Vercel) / ORGX_SERVICE_KEY (Worker secret) - ORGX_API_URL - MCP_JWT_SECRET (Worker secret) - ORGX_INTERNAL_SECRET (Worker secret; must match the OrgX web app runtime secret) - ExistingBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. OrgX MCP's toolset — orgx_bootstrap, orgx_search, orgx_inspect and 11 more — is a fair guide to whether it matches your workflow. It is maintained by com.useorgx; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against OrgX MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| orgx_bootstrap | Establish session context, scopes, and routing guidance. |
| orgx_search | Find entities, decisions, artifacts, and memory. |
| orgx_inspect | Hydrate one entity with execution context. |
| orgx_recommend | Get next-action recommendations or morning brief signals. |
| orgx_write | Create or update durable OrgX records. |
| orgx_attach | Attach proof, URLs, documents, screenshots, or artifacts. |
| orgx_act | Launch, pause, complete, validate, delete, or otherwise act on an entity. |
| orgx_plan | Start, resume, edit, improve, or complete a plan session. |
| orgx_spawn | Guard, classify, spawn, or hand off specialist agent work. |
| orgx_decide | Create, remember, approve, reject, or list decisions. |
| orgx_submit_receipt | Submit durable proof, attribution, quality, or outcome receipts. |
| orgx_emit_activity | Emit append-only execution telemetry. |
| orgx_request_attention | Forward a typed question, permission, approval, or recovery request with native continuation context. |
| orgx_poll_attention | Read the durable answer and client continuation state. |
{
"mcpServers": {
"orgx": {
"command": "npx",
"args": ["-y", "@useorgx/wizard"],
"env": {
"MCP_SERVICE_KEY": "your-value",
"ORGX_SERVICE_KEY": "your-value",
"ORGX_API_URL": "your-value",
"MCP_JWT_SECRET": "your-value",
"ORGX_INTERNAL_SECRET": "your-value",
"OAUTH_CLIENT_ID": "your-value",
"OAUTH_CLIENT_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
pnpm (matches the repo's package manager) - Cloudflare account with Workers enabled - The following environment variables must be configured for both the worker and the Next.js app: - MCP_SERVICE_KEY (Vercel) / ORGX_SERVICE_KEY (Worker secret) - ORGX_API_URL - MCP_JWT_SECRET (Worker secret) - ORGX_INTERNAL_SECRET (Worker secret; must match the OrgX web app runtime secret) - Existing| Variable | Description | Required |
|---|---|---|
| MCP_SERVICE_KEY | Credential the server authenticates with. | Yes |
| ORGX_SERVICE_KEY | Credential the server authenticates with. | Yes |
| ORGX_API_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_JWT_SECRET | Credential the server authenticates with. | Yes |
| ORGX_INTERNAL_SECRET | Credential the server authenticates with. | Yes |
| OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.