Keep credentials private
Manage encrypted provider credentials in a dedicated connection layer, without returning provider secrets to AI runtimes.
Este documento está disponible actualmente en inglés.
OUTBORN AGENT CONNECT
Connect AI agents to MCP servers, apps, APIs, databases, browsers and trusted devices through managed authentication, scoped permissions and auditable execution.
MCP GATEWAY + AGENT ACTION LAYER
A secure MCP gateway and execution layer between AI agents and the tools, data, infrastructure and devices they need to use.
Manage encrypted provider credentials in a dedicated connection layer, without returning provider secrets to AI runtimes.
Use explicit provider capabilities and permission grants to control access to connected systems.
Inspect connection health, resource discovery and recorded operations in one place.
Add a provider account, an MCP endpoint, or a trusted browser or device.
Configure the available capabilities and access. High-impact device permissions need explicit confirmation.
Let your AI runtime use connected capabilities, then review health and activity in Agent Connect.
APPS & INTEGRATIONS
Bring email, data, knowledge, and everyday work into one connected workspace.
ORGANIZATION & AI GOVERNANCE
Give AI access to connected systems with clear ownership and reviewable changes. Use approval rules to put an authorized owner or reviewer in the decision loop.
Assign owners, teams and environments. Review health, change plans and approval policies in one place.
Inspect the intended action, inputs, rationale and impact. Edit or dismiss a pending AI proposal before it runs.
Set allowed approver roles for sensitive actions. Ownership identifies accountability; the policy determines who can approve.
01 / AI REQUESTS
02 / POLICY & APPROVAL
03 / MCP TOOLS & SKILLS
Execution waits · Decision and outcome recorded
In Proposals, approving can immediately execute the change. In Control Center, change plans have separate Approve and Execute actions.
Examples apply to governed provider actions supported by an adapter. Agent Connect manages connections, proposals and operational change controls; Outborn Governance provides the broader governance layer. This is not a blanket approval gate for every AI interaction.
Agent Connect owns connections, credential brokerage and access to systems. Outborn AI owns agent definitions, orchestration and workflows. Outborn Governance owns risk, policy and approval boundaries.
Provider and MCP secrets are encrypted with AES-256-GCM before persistence. Underlying provider secrets are not returned to connected AI runtimes. Supported OAuth MCP connections use PKCE and server-side credential storage.
Provider APIs, remote MCP servers, supported data platforms, browsers and trusted devices. Capabilities vary by adapter. Some entries are beta or catalog-only; ODBC/JDBC execution requires a compatible driver runtime.
One governed action layer for your AI stack.