Every Nexus workflow can be exposed as an MCP server. The moment you publish, it appears in your workspace registry — callable by other workflows, by your in-house agents, and by any external MCP client.
The current draft becomes a frozen, versioned topology. Logic-level changes can ship without a re-publish; structural changes require one.
Inputs and outputs become a JSON schema. Any caller — workflow, agent, or external client — can validate before invocation.
The workflow becomes a tool on your tenant's MCP server: tools/list returns it; tools/call runs it.
Drag-drop the published workflow into another graph. Its schema drives the form designer like any other typed node.
Existing parents stay on their pinned version. New callers default to the latest — but every call site is explicit, never silent.
Who published, what changed since the last version, and a diff of the topology. Required for SOC 2; useful daily.
Once published, your workflow is a first-class member of the MCP ecosystem inside your tenant. The same workflow runs from a parent graph, from a Claude Desktop session, from a Cursor IDE call, and from a custom in-house agent — without you doing anything different.
30 minutes. We'll author a small workflow on your data, publish it, and call it from Claude Desktop — same tenant, same auth, no glue.