Machine Integrations

Machine consumers need stable schemas, bounded scope, and explicit provenance. They should not scrape terminal prose or reconstruct workspace identity from local filesystem guesses.

MCP boundary

npx workspai workspace mcp serve

MCP exposes Workspace Intelligence through the CLI-owned integration boundary. The server projects existing Model, Graph, context, and evidence; it does not become a second mutation or verification authority.

Export, share, and hydrate

npx workspai workspace export --json

npx workspai workspace share --json

npx workspai workspace hydrate --json

Export creates a consumer representation. Share prepares a governed bundle. Hydrate restores supported state only after validating its schema, identity, and compatibility. None of these commands may silently import secrets, dependency trees, or machine-local project links as portable source.

Every integration should preserve omission budgets, evidence references, and the difference between observed, inferred, stale, and unknown facts.

See workspace mcp, workspace export, workspace share, and workspace hydrate.