Organization Integrations

On the Integrations page in the Organization section of Settings, organization admins approve MCP servers for their organization. MCP (Model Context Protocol) lets AITEZA use tools of external systems. People in the organization then connect to the approved servers (see Integrations) and choose per message which integrations AITEZA may use.

Server List#

The page lists the organization’s servers with their URL and a summary line: the authentication type, the number of connected people and, if the server is switched off, Switched off. Servers approved only for certain groups show these groups, for example Only Sales, Purchasing.

• Add server adds a new server.
• Edit opens the server’s settings in a side panel. Changes apply from the next message on.

Suggestions#

Below the server list, Suggestions lists frequently used MCP servers hosted by their vendors: AITEZA Docs, Linear, Notion, Jira & Confluence, Microsoft 365, Microsoft OneDrive, SharePoint, Outlook mail and calendar, Teams and Word, Google Drive, Gmail, Google Calendar, Docs, Sheets, Slides and Chat, GitHub, Slack, HubSpot, Box, Grafana, Figma, Canva and Microsoft Learn. Six are shown first; Show all count suggestions shows the rest. Servers you have already added (same URL) no longer appear.

Each suggestion shows its authentication type and, where it applies, these notes:

• App registration needed: the service does not register AITEZA automatically. Create an app there with the redirect URI shown and enter its client ID and client secret.
• Tenant ID needed: for Microsoft servers, replace the tenant ID placeholder in curly braces in the URL or the authorization server with your Microsoft Entra tenant ID. The form cannot be saved while the placeholder is still there.
• Preview: the vendor still offers the server as a preview.
• Copilot license required: Microsoft’s Agent 365 servers (OneDrive, SharePoint, Outlook, Teams, Word) only admit people with a Microsoft 365 Copilot license, in a tenant enabled for the preview. Without that license, use Microsoft 365.
• Approved apps only: the vendor (currently Figma) admits only applications it approved; sign-in may fail as long as AITEZA is not approved.

Add opens the server form prefilled with name, description, URL, transport and authentication. At the top, it shows the notes and a link to the vendor’s setup guide. Review the settings and save.

Server Settings#

Group Approval#

With Only for certain groups switched on, tick one or more of the organization’s groups. At least one group must be ticked (“Select at least one group.”). Without groups, the server is available to the whole organization.

People outside the selected groups do not see the server in Settings > Integrations or in the chat, cannot connect it, and its tools are never used for them. For example, you can offer OneDrive only to the Sales group and not to Engineering.

If an approved group is deleted, the server is not opened to everyone. It simply has one group fewer; remove the group from the selection.

Authentication Types#

Keys#

For Personal key and Organization key, Key goes into sets where AITEZA sends the key:

• Header: a request header. Enter the Header name (default Authorization) and the Prefix (default Bearer ), the text before the key.
• Basic authentication (username:password): the key is entered as username:password, for example email:api-token.
• URL parameter: a parameter of the server URL. Enter the Parameter name, for example token. Use this only if the service requires it: URLs can end up in proxy and server logs, so a header is the safer choice.

The organization key is write-only. It is stored encrypted and never shown again. To keep the stored key when you edit the server, leave the field empty.

Personal Sign-in (OAuth)#

For Personal sign-in (OAuth), the side panel shows the Redirect URI. If the service requires a registered app (client), register this URI when you create the app there.

Testing a Server#

Test connection tests the saved settings:

• Servers without personal sign-in (organization key or no authentication) are connected, and their tools are listed.
• For servers with personal sign-in, AITEZA discovers the authorization server.
• For servers with personal keys, AITEZA checks that the server can be reached.

Changes That Affect Connections#

• Changing the Server URL, the Client ID or the Authorization server expires everyone’s connection. People then have to reconnect.
• Changing the Authentication type removes all connections.
• Remove deletes the server and all connections to it. The confirmation shows how many people lose their connection.

All changes are recorded in the audit log in the area Administration, with the actions MCP_SERVER_CREATE, MCP_SERVER_UPDATE, MCP_SERVER_DELETE, MCP_CONNECTION_CREATE and MCP_CONNECTION_DELETE. The entries for MCP_SERVER_CREATE and MCP_SERVER_UPDATE include the approved groups.

Microsoft 365#

The suggestion Microsoft 365 is built into AITEZA. It works with every Microsoft 365 business plan; unlike Microsoft’s Agent 365 servers, people need no Microsoft 365 Copilot license. AITEZA reads and writes through Microsoft Graph with each person’s own sign-in, so everyone only sees what they can access in Microsoft 365. Admins manage it like any other server: availability, groups, connections and the audit log work the same.

Its tools search and read mail, list calendar events, search and read files and folders in OneDrive and SharePoint (Word, Excel, PowerPoint, PDF and text files) and find colleagues. Creating and changing drafts, sending and replying to mail, attaching AITEZA files (chat attachments, dataroom files, generated files) to mail, uploading AITEZA files to OneDrive or SharePoint and creating calendar events change data: AITEZA asks the person in the chat before each of these actions. Only files the person can open in AITEZA can be attached or uploaded, and each such access is recorded in the audit log.

AITEZA Docs#

The suggestion AITEZA Docs is built into AITEZA and needs no sign-in or key. With it, AITEZA searches and reads this documentation in English, German and Polish, so it can answer questions on how AITEZA works and link to the matching page. Under Suggestions, select Add next to AITEZA Docs and save; the server is then available like any other, including groups and the audit log. AITEZA loads the published documentation and checks for changes every hour.

Typical Setups#

The exact steps depend on the service. Check its documentation for its MCP endpoint and how apps are registered there.

Services with automatic registration, for example many SaaS MCP servers:

1. Enter the Server URL.
2. Choose Personal sign-in (OAuth).
3. Leave Client ID empty.

Services that need a registered app, for example Microsoft 365 or OneDrive through Microsoft Entra ID, GitHub, Google Workspace, Slack, Box or HubSpot:

1. Choose Personal sign-in (OAuth) and copy the Redirect URI shown.
2. Register an app at the provider with this redirect URI and grant it the permissions it needs. For Microsoft, an administrator usually has to grant admin consent in Entra ID.
3. Enter the Client ID and Client secret of the app and, if needed, the Scopes and the Authorization server.

Services with API keys or personal access tokens:

1. Choose Personal key (or Organization key if everyone should use one shared key).
2. Under Key goes into, choose Header and the header the service expects.

Good to Know#

• Integration tools work only with models that support agent mode (see Organization Models).
• Relay guests never use integrations.
• AITEZA treats the results of integrations as untrusted external content. Tools that change or delete data are used only when a person explicitly asks for it.