Prepare a custom MCP connection.
The empty setup form asks for a Server URL and an optional Auth header. Review the server and its actions before connecting.

Connect the apps and knowledge your team already works with. Give each employee the specific tools its job calls for.
Inside integrations
The empty setup form asks for a Server URL and an optional Auth header. Review the server and its actions before connecting.
Choose a model and voice, then provide the phone number, SIP URI and Twilio credentials. This screen shows setup before connection.
Deploy groups Web & embeds, Phone numbers, Messaging channels, Meetings and Scheduled tasks. In Meetings, review Employee setup, then enter the Meeting URL under Invite & sessions.
Connection surfaces
Configure the employee, presentation, lead form, and available delivery controls in Deploy → Web & embeds. Test the visitor experience before sharing.
Review the provider credentials, number, employee, model, voice, and call persona in Connect phone number. Verify a test call before rollout.
Open Slack setup from Deploy and review the app credentials and destination settings. Verify the completed connection with a message in Slack.
Open WhatsApp setup from Deploy and follow its current connection flow. Confirm the connection and test a message before using it with customers.
Browse connections in Library → Connected tools. Available providers, authentication methods, and actions depend on the connection and your access.
Add a server name and URL in Library. Supply only the headers and authentication the selected server requires, then verify its available tools.
Open Memory & sessions from the account menu to review the context and session records available to your account.
Open Scheduled tasks in Deploy to review schedule creation, task status, and run controls. Verify execution and any destination-system result.
Tool connections
Example workflows include lead review, account context, and follow-up preparation. Check the current catalog, permissions, and supported actions for each provider.
Explore email, calendars, files, documents, and team workspaces. Check the current catalog, permissions, and supported actions for each provider.
Explore support context, issue summaries, and handoff preparation. Check the current catalog, permissions, and supported actions for each provider.
Explore task planning, project context, and follow-up tracking. Check the current catalog, permissions, and supported actions for each provider.
Explore campaign, content, and publishing workflows from approved source material. Check the current catalog, permissions, and supported actions for each provider.
Explore scheduling and meeting preparation. Check the current catalog, permissions, and supported actions for each provider.
Explore creative files, shared assets, structured bases, and planning material. Check the current catalog, permissions, and supported actions for each provider.
Explore product and engineering context for issue review and release preparation. Check the current catalog, permissions, and supported actions for each provider.
Explore customer subscription and commerce context. Check the current catalog, permissions, and supported actions for each provider.
Explore data stores, automation systems, and internal tools through supported connections. Check the current catalog, permissions, and supported actions for each provider.
Aivah agents should only use external tools when the relevant connection, authentication, and permissions are configured. This keeps each employee grounded in your business context and aligned with authorized workflows.
Review enterprise controlsThe right integration starts with the work, then the permissions needed to do it.
Explore supported communication and productivity apps. Check the app's available actions before assigning it to an employee.
Connect a tool