Discover
Inspect the connector’s capabilities, permissions and role.
A client adapter, business-system connection, knowledge source and runtime target play different roles. Start with the task—and choose the right control path.
Discuss an integrationInspect the connector’s capabilities, permissions and role.
Select the intended account or target and resource scope.
Bind eligible capabilities to the project or approved profile.
Inspect health, test the path, reconnect or revoke deliberately.
Keep existing knowledge with its authoritative owner. Use live reads for current permission-bound information, reviewed snapshots for stable releases, or federated retrieval for an existing index. A connector should make the source and mode understandable.
For coding clients, connect approved tools, profiles and scoped resources. For business agents, identify the operation that changes a customer or company system. A voice provider can keep telephony behavior while the governed action path handles a sensitive business request.
Inspect a bounded environment through DriftGate Sync’s local, read-only MCP tools. Preparing an action and authorizing its effect remain separate.
See where control happensAvailable path: read-only Sync MCP inspection. Agent Client Protocol is roadmap direction; client and version support must be qualified separately.
Approved profiles, scoped resources and governed operations on a qualified client path.
A second supported coding context with separate authorization and explicit configuration state.
Repository-scoped knowledge and useful governed actions on selected resources.
Selected knowledge sources, source lineage and reviewed publication boundaries.
Authorized tool discovery and invocation into shared governance—not a second policy engine.
A specifically qualified client protocol and version; not a blanket claim about every ACP.
Waits, callbacks and recovery beneath DriftGate’s authority and evidence model.
Cloud services and deployment patterns with explicit identities and ownership.
Supported model and agent interfaces, qualified independently from other access surfaces.
Scoped knowledge access with explicit source permissions, revisions and sharing boundaries.
Selected project resources through a qualified knowledge or action adapter.
Voice-agent actions governed through specifically supported provider boundaries.