OrgX is coordination infrastructure for AI-native teams. It gives your LLM a persistent organizational layer: initiatives with milestones and tasks, human-in-the-loop decision workflows, specialist agent delegation, and cross-session memory that survives tool switching. What you can do with OrgX via MCP: Scaffold initiatives — decompose a goal into workstreams, milestones, and tasks in one call Manage decisions — create, review, approve, or reject decisions with audit trails Delegate to specialist agents — spawn tasks for domain agents (engineering, marketing, product, sales, operations, design) and monitor their progress Query organizational memory — search past decisions, artifacts, and learnings across initiatives Track progress — get initiative health, agent status, blockers, and morning briefs Plan and prioritize — score queues, get next-action recommendations, and run autonomous sessions with budget guardrails OrgX is built for solo founders and small teams who work across multiple AI tools and lose context between sessions. Instead of manually shuttling context between Claude, Cursor, and ChatGPT, OrgX holds the organizational graph so every tool sees the same state.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C, 47.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 7/10 | initialize answered; tools/list failed.
|
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3399 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 46 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 4% of peers
- This listing 2,283 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Valid MCP handshake −3
— Complete the MCP handshake without errors.
Now: initialize answered; tools/list failed.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/useorgx/orgx-mcp/mcpcurl -X POST https://server.smithery.ai/useorgx/orgx-mcp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'