Integrations and MCP in AI-Public
With integrations, the AI can use information from Google Workspace, Microsoft 365, and MCP servers of your organization. An integration that you enable in Preferences → Tools becomes part of your standard toolset. This means you do not have to start a separate integration chat for every question.
What types of integrations are there?
| Type | Examples | Web | Mobile | Desktop |
|---|---|---|---|---|
| Built-in integrations | Gmail, Google Calendar, Google Drive, Outlook, Teams, and SharePoint | Yes | Yes | Yes |
| Remote MCP | A registered Streamable HTTP server | Yes | Yes | Yes |
| Local MCP | Microsoft 365, Google Workspace, Nextcloud, and Memory via stdio | No | No | Yes |
The organization determines which integrations are available. Users only see options they have access to.
Google Workspace and Microsoft 365
An administrator first makes the Google or Microsoft suite available. Then you can enable the desired integrations in Preferences → Tools and grant permission once.
- Google Workspace can provide Gmail, Google Calendar, and Google Drive.
- Microsoft 365 can provide Outlook Mail, Outlook Calendar, Teams, and SharePoint.
- Access tokens and refresh tokens are encrypted and stored server-side only.
- You can revoke permission later or reconnect the integration.
The integrations are executed by AI-Public and are not tied to a single AI provider. You can use them with OpenAI, Claude, Gemini, and Mistral, as long as the chosen model supports tool usage. With Gemini 3 and newer, suitable Google-native tools and AI-Public tools can be combined in the same context; older Gemini models use only the native toolset when native tools are active.
Using a remote MCP server
Remote MCP servers preferably use Streamable HTTP. The endpoint must be a public HTTPS URL with the full MCP path, usually /mcp. AI-Public rejects redirects, private or local addresses, and endpoints without valid MCP initialization.
After verification, the chat uses only a registered connectorId. The endpoint configuration and secrets are not stored in chats. OAuth tokens and static secrets remain in server-only storage.
Enabling integrations
- Open your profile menu and go to Preferences.
- Open Tools or Integrations.
- Enable an available connector or MCP server.
- Complete the sign-in when prompted.
- Start a regular chat and ask a specific question about the connected source.
In the chat settings, you can see which integrations are available. The AI automatically chooses a suitable tool when needed.
Desktop: local integrations
The desktop app uses the same built-in integrations for Google and Microsoft as web and mobile. Additionally, it can install local stdio MCP servers, for example for Nextcloud, Memory, and other self-chosen services. Local file access is built-in and does not require an MCP server.
Read more at Local integrations in the desktop app.
Privacy and management
- Administrators determine which suites and environment servers are available.
- Users decide which available integrations are personally enabled.
- Server-side credentials are not readable from the browser or mobile app.
- Local desktop secrets are stored encrypted on the device.
- Tool and role access are rechecked at every use.
- Write permissions can create, modify, or delete data; align scopes with the information security policy.
