Nexus — MCP-native orchestration

AI, people, and code — on one graph. Compose agents and workflows by describing them or drawing them. Then govern every run, replay it, and prove what happened. The same platform our vertical products are built on.

Architecture

Built on the Model Context Protocol.

The old way

Four hundred connectors, maintained by hand.

Each one a moving target — auth that changes, fields that drift, breaking releases on someone else's schedule.

The Nexus way

One protocol. Infinite reach.

Add an MCP server. Nexus reads its tools and they appear on the canvas — schemas, config, and all. The vendor maintains it. You don't.

Vendor-maintained connectors
Config generated from schemas
Bring your own MCP server

salesforce.mcp · connected

→ tools/list

← { "tools": [

{ "name": "sf.lead.create" },

{ "name": "sf.lead.enrich" },

{ "name": "sf.opp.update" } …14 more

] }

▸ palette · appeared on canvas

The platform

What sets it apart.

i

Visual canvas

Sixteen node types. Drag to compose. Versioned, replayable, audited.

ii

A2A composition

Workflows call workflows. Build big systems from small ones.

iii

Knowledge grounding

Ground every prompt in your own data, cited and controlled.

iv

Humans on the graph

Forms and approvals as first-class nodes, not afterthoughts.

v

Publish as MCP

Any workflow becomes a server other agents can call.

vi

Replay & observe

Every run recorded. Compare, debug, prove what happened.

The canvas

Describe it, or draw it.

workflow · invoice-reconcilerunning

Nodes

Trigger

Agent

Action

Knowledge

Form

Code

Sixteen node types. Drag to compose. Every run versioned, replayable, and audited.

Governed by default

Built for regulated industries.

SOC 2HIPAAGDPRSingle-tenantAWS-nativeBYOC & on-premAudit & replay

One protocol.
Every service.
Any agent.