Integration architecture
- User authorizes an external provider
- Cloud API resolves active connections
- Session config is injected with MCP server entries
- Runtime exposes tools (directly or through discovery mode)
- Agent invokes tools in normal tool loop
Runtime exposure strategies
| Mode | Behavior |
|---|---|
| Direct exposure | Tools are loaded and callable immediately. |
| Discovery-gated | Tools remain hidden until search/unlock is used. |
Common integration domains
- Gmail and Google Calendar
- Slack
- Developer systems (GitHub, Linear, Notion)
- Additional MCP-compatible services
Security and scope
- Integrations are tied to authenticated user sessions
- Tool availability can be allowlisted per integration
- Revoking integration access removes runtime availability on next injection/update
Operational pattern
When integrations change, Ara updates runtime config and restarts the gateway only when required. This keeps tool state synchronized without forcing full session recreation.Skills + integrations
Best practice is to wrap repeated integration calls in reusable skills.