MCP
Tools and systems the Agent API may call.
Host → client → server → external systems. Broker / gateway security lives in Helix. This is not a marketplace claim and not a public SLA.
Docs · Playbooks
MCP vs Skills.
You talk in tickets, not protocols. MCP is the system surface. Skills are the seated playbook.
Skills
The playbook a seated role already has.
Tone, format, tools, constraints. Role Studio loads the playbook so the buyer describes work. The desk already knows how to sit.
Playbooks
Not a prompt pack store.
A playbook is attached to a desk, versioned in the catalog, and sealed with the pack. It is not a GrokBots directory and not “full marketing team free.”
Tools
Named local kernels on this host.
PromptDiff, Seek, Dissent, Assembler, Seat Token, Outbox, Seal Log, Pack Adapter — analogs you can run without a protocol lesson.
Talk Route is how a human uses both: describe the work, a ticket opens, the swarm sits a desk that already has a skill. If the ticket needs an external system, the Agent API may call MCP. You did not have to name either.