Skip to main content
MCP Connectivity brings the Model Context Protocol into SpineWorkspace. Any MCP server (yours or a third party’s) becomes an available capability that Twin and domain agents can invoke, with the same authorization, scoping, and receipts as any other capability.

​
Why MCP

  • Open standard for exposing tools to AI agents.
  • Custom integrations without building a full connector.
  • Reusable across LLMs and agent runtimes.

​
How It Works

1

Register an MCP server

Point SpineWorkspace at your MCP endpoint and authenticate through One Auth.
2

Capabilities become available

Each MCP tool is projected as a SpineWorkspace capability with scope and inputs.
3

Twin and agents can invoke it

Governed calls flow through the same authorization and receipt path.