Integrations
FuseOne separates integration paths by the kind of control the platform can honestly provide.
MCP servers
Section titled “MCP servers”MCP servers expose tools. Operators choose which tools are visible, and a Curator classifies the effect of each tool before published agents can rely on it.
HTTP MCP traffic refuses environment proxies and blocks cloud metadata and link-local destinations. Stdio MCP servers can be routed through the local egress proxy with a per-server allow-list, and the console shows whether the operator has declared that deployment NetworkPolicy enforces the proxy path.
Governed connectors
Section titled “Governed connectors”Governed connectors are first-party shapes. They are used when the platform should own the operation contract, secret handling, storage semantics and approval posture instead of delegating all of that to an MCP server.
Vault and governed PostgreSQL reads have runtime adapters. SQL exposes only
registered read-only templates: the model supplies a template id and typed
parameters, while the worker obtains one short-lived credential from the
configured Vault database role after the Gate allows the call. The credential
never becomes tool input or output, and every execution uses a new connection
and lease. PostgreSQL enforces the same deadline as the worker. PostgreSQL text
is the fallback for every result type, so driver internals never become part of
the governed record. UUID, network, exact numeric and bigint values remain
lossless strings; explicitly safe JSON stays structured, and binary values are
base64. The connector fixes date, interval, timezone, float and bytea session
settings as well, so database defaults cannot change that representation.
The catalogue also names planned shapes for object storage, identity actions, DNS, Kubernetes, SMTP and governed HTTP. A catalogue entry is not the same as a ready runtime adapter; the console must not imply a connector is operational until the runtime exists.
In this first SQL slice, administrators write the database target, Vault binding and registered templates through the connector administration API. The console lists the safe target, role and template count, but deliberately does not offer a partial editor that could omit the query contract.
Channels
Section titled “Channels”Channels are how people talk to agents and how agents report back. Channel delivery is operational evidence, not a run step. The runtime cockpit can show stable channel failure codes without exposing conversation identifiers.
Native platform tools
Section titled “Native platform tools”Some tools are part of FuseOne itself: memory, context sharing and duplicate effect recognition. They are governed by the same Gate and label rules as external integrations.