One platform, many tools
A Living Map of What Ai1 Connects To
Each tile is a real integration. The set below is what we connect to most often, and it grows every week. Hover, tap, or focus any tile to see its name. On a phone, the same set becomes a tappable grid.

The Connector Catalog
Roughly 90 tools across about 20 categories. Named tools are illustrative, not exhaustive. Anything with an API or an MCP server can be added.
Intelligence (bring your own model)
Communication & productivity
CRM
Project & task management
Video meetings
AI notetakers
Phone & VoIP
Social
Paid ads
Email marketing
Analytics & SEO
Scheduling & booking
Helpdesk & support
Accounting
E-commerce & payments
Forms & surveys
CMS & website
Hosting & infrastructure
Code & DevOps
Domains & DNS
Advanced / on request
The catch-all rule: if it exposes an API or an MCP server, your agents can connect to it. The list above is what we connect to most often, and it grows every week.
Under the hood
How a Connection Works
Three standard paths, your credentials, no lock-in. You connect a tool once and your agents can use it from then on.
REST APIs
Most tools expose a REST API. Your agents read and write through it directly, using a token you supply, so data flows straight between your tools and your deployment.
MCP servers
A growing standard for giving agents safe, structured access to a tool. If a tool ships an MCP server, Ai1 can speak to it natively, with clear, auditable actions.
OAuth & your tokens
You authorize with OAuth or paste a token during onboarding. Credentials are encrypted at rest, and you can revoke access at any time. You stay in control of what is connected.
Connecting a tool does not move your data into a shared system. Your integrations run inside your dedicated single-tenant deployment, with your keys, on your server.
