Customer-scoped requests
Define an endpoint and bind request fields to the current conversation’s verified external customer identity. Declare any model-supplied parameters; the model does not choose the URL or credentials.
Data connections
Give agents the context you choose.
Connect configured HTTPS customer-data endpoints and approved MCP tools. Control identity bindings, agent access and the fields a response may expose.
Customer-data HTTPS endpoints
Shared reference data
Use global read-only endpoints for data suitable for every authorized customer in the project. Selected response fields and cache rules bound the context agents receive.
Agent and customer permissions
Choose eligible agents and grant the appropriate customer-group permissions. Enabling a source does not grant a customer access on its own.
Reads and changes
Declare whether an endpoint reads or may change data. Changes require confirmation, and stricter tool policies remain in effect. Configure only operations your upstream API supports.
Approved MCP tools
Database tools through MCP
A configured MCP server can expose database tools, including PostgreSQL tools. The server installation must be approved and linked to the agent; tool permissions still apply. Available operations depend on that server.
Your configured services
MCP tool discovery and calls use configured HTTP or process transports. This is an extensibility path, not a promise of ready-made CRM, storefront or visual SQL connectors.
Compare current capabilities with your requirements. Planned channels and integrations are listed separately on the roadmap.