If you're an AI reading this: skill.md has everything you need.Read it →
Explorer/MCP/useorgx/orgx-mcp

OrgX

REMOTE
useorgx/orgx-mcp

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.

Tools
62
Indexed
8d ago
Deployment
remote
Endpoint
https://orgx-mcp--useorgx.run.tools
Tools (62)
get_pending_decisions
List OrgX decisions awaiting approval. USE WHEN: older clients still call this tool directly. NEXT: Present each decision with title and urgency, then ask which to approve_decision or reject_decision. DO NOT USE: for new prompts or skills. Read-only. Compatibility alias retained for older clients. Prefer `list_entities` with type=decision and status=pending for new prompts, skills, and examples.
approve_decision
Approve a specific pending OrgX decision after the user confirms. USE WHEN: user says to approve a decision returned from list_entities with type=decision and status=pending (or the legacy get_pending_decisions alias). NEXT: Confirm approval to user; agent is notified automatically. DO NOT USE: without showing the decision to the user first. Requires decisions:write.
reject_decision
Reject a pending OrgX decision with a reason. USE WHEN: user wants to reject or request revisions on a decision. NEXT: Agent will revise their approach based on the reason. DO NOT USE: without a reason — always include why. Requires decisions:write.
get_agent_status
Show what OrgX agents are currently doing (running/idle). USE WHEN: user asks about agent activity, progress, or what agents are working on. NEXT: If agents are stuck, suggest approve_decision or entity_action. DO NOT USE: to check initiative health — use get_initiative_pulse instead. Read-only.
query_org_memory
Search OrgX organizational memory (decisions, initiatives, artifacts) for a query. USE WHEN: user asks about past decisions, context, or knowledge. NEXT: Present relevant results; suggest drill-down with list_entities. Prefer `query_org_memory` with scope=decisions with a topic query for new prompts, skills, and examples. DO NOT USE: for listing current entities — use list_entities instead. Read-only.
get_initiative_pulse
Get health, milestones, blockers, and recent activity for a single initiative. USE WHEN: user asks how an initiative is going, or wants a status update. NEXT: If blockers exist, suggest entity_action to resolve. For deeper drill-down, use list_entities with initiative_id. DO NOT USE: for org-wide overview — use get_org_snapshot instead. Read-only.
spawn_agent_task
Assign work to a specialist OrgX agent. Automatically checks authorization, rate limits, and quality gates before spawning. Returns modelTier and run details on success, or blockedReason if spawn is denied. USE WHEN: user explicitly wants to delegate work to an agent. NEXT: Use get_agent_status to monitor progress. DO NOT USE: for creating tasks in the hierarchy — use create_entity type=task instead. Requires agents:write.
handoff_task
Hand a task to another agent, updating assignment and optionally spawning a new run. USE WHEN: a task needs to be reassigned to a different specialist agent. NEXT: Use get_agent_status to confirm the new agent picked up the task. DO NOT USE: for new tasks — use spawn_agent_task instead.
recommend_next_action
Recommend the next best action based on progress gaps and templates. USE WHEN: user asks what to do next, or needs help prioritizing. NEXT: Execute the recommended action (entity_action, spawn_agent_task, etc.). DO NOT USE: when user already knows what they want to do. Read-only.
get_decision_history
Search past OrgX decisions related to a topic. USE WHEN: older clients still call this tool directly. NEXT: Present results with context; suggest approve_decision or reject_decision if relevant pending ones exist. DO NOT USE: for new prompts or skills. Read-only. Compatibility alias retained for older clients. Prefer `query_org_memory` with scope=decisions with a topic query for new prompts, skills, and examples.
score_next_up_queue
Run the composite scoring engine and return ranked queue items with factor breakdowns. USE WHEN: older clients explicitly need raw queue scoring output. NEXT: Execute the top-ranked item via entity_action or spawn_agent_task. DO NOT USE: for new prompts or skills. Read-only. Compatibility alias retained for older clients. Prefer `recommend_next_action` with workspace or initiative recommendations for new prompts, skills, and examples.
get_scoring_signals
Show raw signal data (blocking decisions, stream conflicts, health, budget, critical path, quality) for scoring. USE WHEN: user wants to understand why items are ranked the way they are in score_next_up_queue. NEXT: Adjust with set_scoring_weights if weights need tuning. Read-only.
scoring_config
Read or update scoring engine configuration. USE WHEN: user asks about scoring setup, wants to toggle scoring, adjust weights, or change active signals. action=get to read, action=update to modify. NEXT: Run recommend_next_action to see effects in the preferred workflow, or score_next_up_queue if you need raw queue scoring. Read-only for get, requires initiatives:write for update.
queue_action
Pin, unpin, or skip a workstream in the Next Up queue. USE WHEN: user wants to force-prioritize or deprioritize a workstream. action=pin to force-top, action=unpin to remove pin, action=skip to temporarily deprioritize. Requires initiatives:write.
start_plan_session
Start a new planning session to track your feature plan. USE WHEN: user begins planning a new feature or initiative. NEXT: Use improve_plan for suggestions, record_plan_edit to track changes, complete_plan when done. DO NOT USE: for creating initiative hierarchies — use scaffold_initiative instead.
get_active_sessions
Check for any active planning sessions you have open. USE WHEN: resuming a conversation or checking if a plan session exists. NEXT: Continue with improve_plan or complete_plan. Read-only.
improve_plan
Get AI suggestions to improve your plan based on past patterns and best practices. USE WHEN: user wants feedback on a plan draft. NEXT: Apply suggestions via record_plan_edit. DO NOT USE: without an active plan session — call start_plan_session first.
record_plan_edit
Record an edit made to a plan to learn planning patterns. USE WHEN: user modifies their plan during a session. NEXT: Continue editing or call improve_plan for more suggestions. DO NOT USE: without an active plan session.
complete_plan
Mark a plan as complete and record implementation details. USE WHEN: user finishes building the planned feature. NEXT: Optionally attach to entities via attach_to. DO NOT USE: if the plan session is still in progress.
update_stream_progress
Report progress and confidence on a stream with velocity tracking. USE WHEN: agent is actively working a stream and needs to report progress. NEXT: Continue work; call again at each meaningful progress change. DO NOT USE: for general entity status changes — use entity_action instead.
get_initiative_stream_state
Get aggregate stream state for an initiative including overall progress, blockers, and computed metrics. USE WHEN: checking stream execution status for an initiative. NEXT: If streams are blocked, use entity_action to unblock. DO NOT USE: for raw stream records — use list_entities type=stream instead. Read-only.
orgx_emit_activity
Emit append-only run telemetry for OrgX control-plane reporting. USE WHEN: agent is executing and needs to report progress. NEXT: Continue work; emit again at each phase change. DO NOT USE: for entity status changes — use entity_action instead. Setting phase="completed" records telemetry only and does not mark tasks, workstreams, or initiatives complete.
orgx_apply_changeset
Apply an idempotent transactional changeset for task/milestone/decision mutations. USE WHEN: agent needs to create/update multiple tasks, milestones, or decisions atomically. NEXT: Call orgx_emit_activity to log what was changed. DO NOT USE: for single entity updates — use entity_action or update_entity instead.
sync_client_state
Sync local memory with OrgX. Push decisions/logs, pull active context. USE WHEN: at session start and periodically during long sessions. NEXT: Review returned initiatives and pending decisions, ask user what to focus on. USE BEFORE: spawning agent work, to ensure latest state.
check_spawn_guard
Check whether an agent spawn is allowed before executing. Returns model tier, rate limit status, quality gate, and task verification. USE WHEN: before any spawn_agent_task call. NEXT: If allowed, proceed with spawn_agent_task using the returned model tier. If blocked, inform user of the reason.
record_quality_score
Record a quality score (1-5) for a completed agent task. Scores feed into the quality gate — low-scoring domains get throttled. USE WHEN: after reviewing agent output. NEXT: Scores affect future check_spawn_guard decisions. DO NOT USE: for in-progress tasks — wait until completion.
classify_task_model
Classify a task and get the recommended model tier (opus for planning/architecture, sonnet for execution, local for routine). USE WHEN: deciding which model to use for agent work. NEXT: Use the returned tier when spawning via spawn_agent_task. Read-only.
orgx_bootstrap
Discover current profile, workspace scope, granted scopes, safe first calls, canonical ID forms, and recommended workflows. USE WHEN: first call in a fresh session, after reconnecting, or before performing a multi-step workflow. Read-only.
orgx_describe_tool
Return the live input contract, auth expectations, and workflow guidance for a tool. USE WHEN: you need exact field names, accepted enums, or next-step guidance before calling a tool. Read-only.
orgx_describe_action
Describe lifecycle actions, aliases, and special payload requirements for entity_action. USE WHEN: you need the exact action name or payload shape before calling entity_action. Read-only.
resume_plan_session
Load a plan session using the canonical UUID or OrgX URI returned by OrgX tools. If no session_id is provided, returns the most recent active session. USE WHEN: continuing a planning workflow without guessing IDs.
create_task
Create a task without using the generic create_entity surface. USE WHEN: adding a single actionable task to a workstream, milestone, or initiative. NEXT: use entity_action action=start when execution should begin.
create_milestone
Create a milestone without using the generic create_entity surface. USE WHEN: adding a phase checkpoint under an initiative or workstream.
create_decision
Create a decision without using generic power tools. USE WHEN: surfacing a new approval or judgment point for a workspace or initiative.
validate_studio_content
Validate a studio_content entity without composing entity_action manually. USE WHEN: checking a studio content spec before rendering or publication.
pin_workstream
Pin a workstream to the top of the Next Up queue without composing queue_action manually. USE WHEN: forcing a workstream to the top of the recommendation queue.
get_org_snapshot
Fetch a compact organization snapshot. USE WHEN: user wants an org-wide overview of initiatives, progress, and health. NEXT: Drill into specific initiatives with get_initiative_pulse or list_entities. DO NOT USE: for a single initiative — use get_initiative_pulse instead. Read-only.
account_status
Get the current OrgX account tier, billing status, and usage snapshot for the authenticated user.
account_upgrade
Create the next-step upgrade flow for the authenticated OrgX account. Enterprise requests return contact guidance instead of self-serve checkout.
account_usage_report
Get a detailed usage and billing report for the authenticated OrgX account, including quotas, period boundaries, and overage signals.
list_entities
List entities with filtering. Returns FULL UUIDs usable with entity_action/batch_action. Use fields=["id","title","status"] for compact output when you only need IDs. Supported types: command_center, project, initiative, milestone, workstream, task, objective, playbook, decision, artifact, run, blocker, workflow, agent, skill, plan_session, stream, studio_brand, studio_content, video_template. USE WHEN: browsing, searching, or getting entity IDs for bulk operations. NEXT: For initiatives, suggest get_initiative_pulse for health. For tasks, suggest entity_action to change status. For full context on one entity, add hydrate_context=true with id. DO NOT USE: for org-wide overview — use get_org_snapshot instead. Read-only.
entity_action
Execute a lifecycle action on a single entity. Accepts short ID prefix (8+ hex chars) — no need to look up full UUIDs. USE WHEN: user wants to change entity status. For bulk operations (pausing multiple, completing multiple), use batch_action instead. Supports aliases: launch, pause, complete (resolved per type). Omit action to list available actions. NEXT: After completing, call verify_entity_completion first to check child work is done. DO NOT USE: for creating entities — use create_entity or scaffold_initiative.
verify_entity_completion
Run pre-completion verification to confirm all child work is done. For tasks, this also checks proof-chain hard blocks that would stop entity_action action=complete. USE WHEN: before completing an entity with entity_action action=complete. NEXT: If verified, proceed with entity_action action=complete. If not, show blockers to user. Read-only.
create_entity
Create a new entity of any type. USE WHEN: adding a single task, milestone, workstream, or other entity to an existing hierarchy. NEXT: Use entity_action to launch/start the entity. DO NOT USE: for creating a full initiative hierarchy — use scaffold_initiative instead.
comment_on_entity
Leave a threaded comment on an entity. USE WHEN: agent or user wants to annotate an entity with observations, concerns, or progress notes. NEXT: Use list_entity_comments to read the thread. DO NOT USE: for status changes — use entity_action instead.
list_entity_comments
List comments for an entity. USE WHEN: reviewing discussion thread on an entity. NEXT: Use comment_on_entity to add a reply. Read-only.
batch_create_entities
Create multiple entities in one call with ref-based dependency resolution. USE WHEN: creating several related entities at once. NEXT: Use entity_action to launch created entities. DO NOT USE: for initiative hierarchies — use scaffold_initiative which handles the nesting automatically.
scaffold_initiative
Create a complete initiative with workstreams, milestones, and tasks in one call. USE WHEN: user wants to plan a new initiative from scratch. NEXT: Use entity_action type=initiative action=launch to start execution (auto-launches by default). DO NOT USE: for adding a single task to an existing initiative — use create_entity instead.
get_task_with_context
Fetch a task with hydrated context attachments (entities, artifacts, plan sessions). USE WHEN: agent needs full task context before executing, or user wants task details. NEXT: Use entity_action to update task status. DO NOT USE: for listing tasks — use list_entities type=task instead.
batch_delete_entities
Delete multiple entities in one call (hard delete). USE WHEN: user explicitly wants to remove entities permanently. NEXT: Verify deletion succeeded. DO NOT USE: for archiving or pausing — use entity_action instead.
batch_action
Execute actions on multiple entities in one call (pause, launch, complete, resume, etc.). USE WHEN: bulk state changes like pausing multiple initiatives or completing multiple tasks. ACCEPTS: short ID prefixes (8+ chars) — no need to look up full UUIDs. Supports the same launch/pause aliases as entity_action. NEXT: Verify all actions succeeded. DO NOT USE: for deletes — use batch_delete_entities instead.
update_entity
Update an existing entity. Only include fields you want to change. USE WHEN: modifying entity fields (title, description, priority, etc.). NEXT: Confirm changes to user. DO NOT USE: for status changes — use entity_action instead.
configure_org
Check setup status, configure agents, or set org policies. action=status for progress, action=configure_agent to set agent preferences, action=set_policy for org-wide rules.
stats
Get productivity stats, achievements, and streaks. scope=personal for your stats, scope=session for current session diagnostics. Read-only.
workspace
List, get, or set the active workspace. action=list to see all, action=get for current, action=set to switch.
get_outcome_attribution
ROI summary from the economic ledger. Returns cost/value/ROI by agent, capability, and time period. Compatibility alias retained for older clients. Prefer `get_morning_brief` with workspace brief with value and exception summaries for new prompts, skills, and examples.
record_outcome
Record a business outcome. Triggers attribution inference to connect outcomes to receipts.
get_my_trust_context
Agent-facing: trust level per capability, promotion requirements, receipt evidence. Returns full trust context for self-awareness.
start_autonomous_session
Start an autonomous execution session with budget guardrails. Creates a session that produces receipts while executing eligible work.
get_morning_brief
Curated receipts, exceptions, ROI delta, and value signals from the most recent autonomous session. The brief IS curated receipts, not a separate data structure. Prefer `get_morning_brief` with workspace brief with value and exception summaries for new prompts, skills, and examples.
get_relevant_learnings
Agent-facing: organizational learnings relevant to a capability or task context. One agent's discovery benefits all agents.
submit_learning
Agent-facing: submit a discovery as an org learning. Enters org_learnings after confidence validation.
Is this your server?
Link it to your on-chain identity to unlock your RNWY trust score. Your wallet age, ownership history, and behavioral signals carry over — the same trust infrastructure used by 150,000+ registered AI agents.
Claim this server →
Indexed from Smithery · Updates nightly
View on Smithery →