14 — MCP, Continuity Bridge, Marketplace and SDK

Canonical reference: 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md §23
Status: Canonical

---

1. Concepts must remain distinct

IW Spine Network MCP, MCP Pool and Continuity Bridge are distinct concepts.

2. IW Spine Network MCP

The hosted remote MCP boundary exposes provider-neutral IntegrateWise resources and tools to approved external AI surfaces. It can provide Spine queries, context projections, history/relationships, knowledge/memory retrieval, capability discovery, proposal submission, governed execution requests and execution/reconciliation status.

MCP tools do not receive direct storage credentials. They call versioned platform APIs and governed capability paths.

3. MCP Pool

MCP Pool is the inward-facing tenant registry of approved external MCP servers/tools, their schemas, trust profile, authorization references, health and delegated scopes. It is principally an enterprise/Customer Zero control concept, not the user-facing product.

4. Continuity Bridge

IntegrateWise — Continuity Bridge is the distribution/access product for external AI hosts. It opens governed context and capability access without making MCP itself the product.

Distribution surfaces can include ChatGPT, Claude, Perplexity, direct MCP clients, embedded enterprise applications, SDK/ADK integrations, provider marketplaces and direct APIs. All must bind to the same identity, tenancy, Spine, projection, capability, governance and audit contracts.