INTEGRATIONS

Keep your agents. Connect their control plane.

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 integration
FROM CONNECTION TO GOVERNED USE

More than a logo in a catalog.

01

Discover

Inspect the connector’s capabilities, permissions and role.

02

Authorize

Select the intended account or target and resource scope.

03

Assign

Bind eligible capabilities to the project or approved profile.

04

Operate

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.

Start in the tools you already use.

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 happens

Available path: read-only Sync MCP inspection. Agent Client Protocol is roadmap direction; client and version support must be qualified separately.

ClaudeProject helper
Project conversation
Maya · Engineer

Claude can see the project helper. Can it change a customer account?

Claude

The reviewed helper can prepare a request. A customer-account change uses the qualified business-system operation.

DriftGate

The project tool and account write have different boundaries.

Two distinct checksScope review
Project tool
Reviewed for discovery
Account change
Checked at submit path
Maya · Engineer

Prepare a draft for account AC-42; don't submit it yet.

Claude

Draft ready. No customer record changed. The exact operation can be evaluated when you choose to submit.

Ready
  1. Maya
  2. Claude
  3. DriftGate
  4. Customer account adapter
  5. Outcome
⌘AI clients

Codex

Approved profiles, scoped resources and governed operations on a qualified client path.

Solo launch focus
✳AI clients

Claude Code

A second supported coding context with separate authorization and explicit configuration state.

Solo launch focus
↗Tools & knowledge

GitHub

Repository-scoped knowledge and useful governed actions on selected resources.

Initial resource set
NTools & knowledge

Notion

Selected knowledge sources, source lineage and reviewed publication boundaries.

Initial resource set
⋈Protocols

MCP

Authorized tool discovery and invocation into shared governance—not a second policy engine.

Access surface
⌁Protocols

Agent Client Protocol

A specifically qualified client protocol and version; not a blanket claim about every ACP.

Roadmap
≋Infrastructure

Temporal

Waits, callbacks and recovery beneath DriftGate’s authority and evidence model.

Durable workflow substrate
⛶Infrastructure

Google Cloud

Cloud services and deployment patterns with explicit identities and ownership.

Selected cloud direction
◎AI providers

OpenAI

Supported model and agent interfaces, qualified independently from other access surfaces.

Provider integration direction
△Tools & knowledge

Google Drive

Scoped knowledge access with explicit source permissions, revisions and sharing boundaries.

Roadmap
◒Tools & knowledge

Linear

Selected project resources through a qualified knowledge or action adapter.

Roadmap
〰AI providers

Retell

Voice-agent actions governed through specifically supported provider boundaries.

External-agent roadmap
BUILD WITH INTENTION

Your next agent.
A better starting point.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps