Skip to content

Spine Workspace

Your host is where you work. Spine is where context continues.

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.

01

What “host connected” actually means

Host identified

The connected host and authenticated user are associated with the correct workspace.

Capabilities discovered

The host exposes a defined set of apps, tools, or MCP capabilities that can be inspected and used within scope.

Permissions resolved

The user, tenant, host, resource, and operation are evaluated before context or actions are made available.

Context flowing

Permitted signals or records have been accepted and processed into an appropriate Spine Fabric state—not merely submitted to a queue.

Work verified

Actions have a recorded outcome and, where supported, readback or reconciliation evidence.

02

Connect in four steps

  1. 01

    Open your host's custom MCP connection experience, if available.

  2. 02

    Add the configured Spine Network MCP endpoint or select the published listing when available.

  3. 03

    Authenticate with One Auth and choose the correct workspace.

  4. 04

    Review available capabilities and verify the connection in the host and Workbench.

03

What the connection view should show

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

Move from understanding to the right next step.