The connection lifecycle
Every new agent or workspace view should not require a new copy of the same integration. Where an authorized host already provides a connector, Spine can use that capability path and preserve the business context around it.
Explore categories such as CRM, communications, productivity, support, finance, storage, data, developer tools, and MCP. Filter by provider, operation, connection type, and actual availability.
An existing host connection exposes supported resources or tools; the host retains underlying connection authority.
A supported direct connection can be configured through the applicable approved OAuth or credential flow.
A compatible server exposes tools under its own protocol and authorization requirements.
Discover → Review → Authorize → Test → Use → Monitor → Refresh or Revoke. Each transition has a meaningful state. “Available” is not “Connected.” “Connected” is not “Synced.” “Synced” is not permission to execute every operation.
Spine can describe a business intent such as updating an account or fetching customer context while the selected adapter maps the operation to provider-specific resource types and traits. The provider's actual support and authorization still determine the result.
Continue with context
Historical recall does not grant authority. Scoped access and explicit approval still apply.
Capability availability varies by tenant, host, and profile. Marketing describes design intent unless a page states verified evidence.