Host identified
The connected host and authenticated user are associated with the correct workspace.
Spine Workspace
Your AI host may already connect to documents, messages, tools, and MCP servers. Spine Workspace can complement that environment by creating a governed bridge to linked business context and continuity.
The connected host and authenticated user are associated with the correct workspace.
The host exposes a defined set of apps, tools, or MCP capabilities that can be inspected and used within scope.
The user, tenant, host, resource, and operation are evaluated before context or actions are made available.
Permitted signals or records have been accepted and processed into an appropriate Spine Fabric state—not merely submitted to a queue.
Actions have a recorded outcome and, where supported, readback or reconciliation evidence.
Open your host's custom MCP connection experience, if available.
Add the configured Spine Network MCP endpoint or select the published listing when available.
Authenticate with One Auth and choose the correct workspace.
Review available capabilities and verify the connection in the host and Workbench.
Host · Connected account · Workspace · Last verified connection · Available capabilities · Permitted scopes · Sync or processing state · Needs attention.
A connected badge should never be used as proof that every downstream source has been ingested or synchronized.
Continue with context