MCP & Connectors
Expose tools and external systems through governed invocation boundaries.
Primitive's reuse architecture already recognises MCP/invocation pathways. The target is to let tools and external systems plug into Primitive without bypassing context, authority or execution records.
MCP and connectors are adapters. They let Primitive use another tool, but the adapter should not get to ignore Primitive's rules just because it lives somewhere else.
Connection is not authority. MCP can describe callable tools/context, while Primitive still decides what a particular agent or task may invoke. The design therefore puts connector discovery outside the consequential effect boundary and permission checks at invocation/execution time.
Reuse layer
The canonical reuse indexes explicitly map MCP and invocation pathways alongside Skills, Tools, Router and Harness components.
Permit integration
The HOLARCHY programme includes a Workspace permit/MCP packet in which work claim/boot/finish behavior is tied to scoped task permits.
Provider neutrality
Connectors should adapt external capabilities into stable Primitive contracts rather than leaking each provider's object model across the OS.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.