Tools
Via the Tools tile in the admin environment, you configure which tools and integrations are available per AI provider. This determines which additional capabilities the AI can use in a conversation, such as searching the internet, creating images, doing calculations, planning routes, or recording information.
The page opens on MCP. After that, the provider tabs from the model settings follow. If a provider is disabled there, the corresponding tool tab does not appear.
Microsoft organization app and write actions
Do you want to offer Microsoft 365 through your own organization app? Follow Set up Microsoft 365. It contains the required Entra app, Graph permissions, organization consent, Identity Provider, and redirect URLs for AI-School, AI-Corporate, and AI-Public.
Under MCP → Suite shortcuts → Microsoft 365, you make the integrations available. If the suite is turned off, the underlying rows are hidden. In the Write actions column, choose per integration Drafts, Send, Write, or Post; only released actions can be performed. Click Save. Users only turn their available integrations on or off in Preferences.
Page structure
The page is divided into tabs per provider, plus a separate MCP tab:
| Tab | Meaning |
|---|---|
| MCP | Manage suites and MCP servers for the environment |
| OpenAI | Tool settings for OpenAI models |
| Claude | Tool settings for Claude models |
| Google (Gemini) | Tool settings for Gemini models |
| European AI | Tool settings for European models such as Mistral |
Per tab, depending on the provider, you manage:
- Native tools (built-in provider tools)
- Universal tools (tools from AI-Corporate)
On the MCP tab, you manage MCP servers at environment level. These are separate from the provider-specific tool settings.
The explanation for an individual tool is shown in the info button next to the tool name. This keeps the page compact, while administrators can still view extra context per tool.
Google and Microsoft connectors
Under MCP → Suite shortcuts, you make Google Workspace and Microsoft 365 available or unavailable as a group. This manages the provider-independent AI-Corporate integrations for the environment; an administrator does not log in on behalf of all employees here.
Employees enable available connectors personally via Preferences → Tools and grant consent once there. Their tokens are stored server-side and remain usable in new chats and on other devices.
Examples of available MCP connectors:
- Google Calendar
- Gmail
- Google Drive
- Microsoft Teams
- Outlook Calendar
- Outlook Mail
The Google and Microsoft tools are executed by AI-Corporate and are not tied to OpenAI. Employees can use them with OpenAI, Claude, Gemini, and Mistral, as far as the selected model supports tool use.
Google Calendar, Gmail, and Google Drive: own Google app
Google Calendar, Gmail, and Google Drive require read permissions that Google classifies as sensitive or restricted. These are only available through an internal Google app of your own organization. Without your own app, they are greyed out and the Google Workspace suite in MCP → Suite shortcuts is not available. Signing in with Google and storing files on a user's own Google Drive still work through AI-Corporate's central app.
An internal app (Internal user type) does not need to be verified by Google and does not require a security assessment. Only accounts within your Google Workspace can use it to sign in and connect. It works like the own Entra app for Microsoft:
- In Google Cloud, in a project of your own organization, create an OAuth consent screen with user type Internal. Add the scopes
openid,email,profile,calendar.events.readonly,drive.file,drive.readonly, andgmail.readonly, and enable the Gmail API, Google Drive API, Google Calendar API, and Google Picker API. - Create an OAuth client of type Web application with these two authorized redirect URIs:
https://ai-corporate.firebaseapp.com/__/auth/handler(sign in with Google)https://europe-west1-ai-corporate.cloudfunctions.net/completeConnectorOAuth(connectors)
- Provide the client ID and client secret through the agreed secure channel. The platform administrator will set them on the Google provider of your environment tenant in Google Cloud Identity Platform, enable the Google sign-in method under Admin → Environment → Tenant, and fill in the Google Workspace domain, for example
company.nl. - After that, you can enable Google Calendar, Gmail, and Google Drive. Employees with a previous Google connection reconnect their Google account once.
Signing in with Google will then also use the own app and show only accounts from the configured domain.
MCP servers for the environment
On the MCP tab, you can first open a store with suitable presets via Add MCP server. The web app only shows servers that can work via a public Streamable HTTP connection. Use Add your own MCP server to open the manual form.
Use the full HTTPS endpoint, including the MCP path such as /mcp. The backend checks DNS, private addresses, redirects, and the MCP handshake. After registration, chats only use a connectorId; endpoints and secrets are not stored in the chat configuration.
An MCP server configured here appears on the dashboard under Tools for users who are allowed to see MCP connections. They see these environment servers alongside their own personal MCP servers and can start a chat with them directly.
Employees cannot edit or delete environment servers themselves. They can, however, turn an available server on or off personally. Management is handled centrally via Admin environment → Tools → MCP.
As an administrator, you can edit, enable or disable, and delete a configured server in this list. Users who have enabled the server keep it enabled. If you change the endpoint or authentication method, re-enter the secret and users will sign in again via OAuth. A disabled server is no longer available to users.
Environment servers are only visible to users who have access to MCP connections. This access is determined by the environment limits and any individual settings for employees.
Native tools
Native tools are built-in tools from the provider itself. They are not executed by AI-Corporate, but are offered by the provider with the model.
| Tool | Provider | Description |
|---|---|---|
| OpenAI Web Search | OpenAI | Searches for current information via OpenAI's built-in web search |
| OpenAI Code Interpreter | OpenAI | Runs Python code for data analysis, calculations, and visualizations |
| Claude Web Search | Claude | Searches for current information via Claude's built-in search |
| Claude Web Fetch | Claude | Retrieves content from web pages and PDF documents |
| Claude Code Execution | Claude | Runs Bash and Python code in a secure sandbox |
| Gemini Google Search | Searches for current information via Gemini's built-in Google Search | |
| Gemini Code Execution | Runs code for calculations and data analysis | |
| Gemini URL Context | Retrieves content from URLs for additional context | |
| Gemini Google Maps | Uses Google Maps for location information, routes, and places |
Gemini 3 and newer models can combine suitable Google-native tools with universal tools and Google or Microsoft connections from AI-Corporate. For older Gemini models, universal tools are disabled in a context with active native tools to prevent incompatible tool combinations.
Code execution tools, such as OpenAI Code Interpreter, Claude Code Execution, and Gemini Code Execution, are off by default. Enable them deliberately when code execution, calculations, data analysis, or file editing is needed.
Universal tools
Universal tools are available for providers where they technically fit and are offered by AI-Corporate itself. For each provider, you choose what happens per tool.
| Tool | Description |
|---|---|
| Create image | Generates images based on a text description |
| Create practice questions | Automatically creates test or practice questions about a text or topic |
| Search the internet | Searches the internet for current information |
| Search images | Searches the internet for images based on a search term |
| Get weather | Retrieves the current weather forecast for a location |
| Check AI content | Analyzes whether a text may have been generated by AI |
| Search Wikipedia | Searches Wikipedia for encyclopedic information |
| Google Routes | Plans routes and calculates travel times |
| Google Places | Finds information about locations and businesses |
| Wolfram Alpha | Performs complex calculations and scientific analyses |
| Logging | Saves important information as an editable note with the chat |
Some internal tools, such as chat_history_search, do not appear in this overview. They are automatically available to the assistant and follow the same environment, user permissions, and retention period. Administrators cannot manage them separately through the tool settings.
Setting per tool
For each tool, you choose one of four values:
| Setting | Meaning |
|---|---|
| Automatic | The AI decides for itself whether the tool is useful for the question |
| On | The tool is always enabled in the relevant context |
| Off | The tool is disabled and cannot be used |
| Not visible | The tool disappears completely from the user interface and from personal preferences |
In most cases, Automatic is the recommended choice. Choose On only when a tool is almost always needed in that context.
In their preferences, users can only set personal exceptions for visible tools. They cannot override the environment setting for tools that are set to Not visible.
Reset and save
Via Restore default values, you reset the tool settings of a provider to the default settings of AI-Corporate. Changes are saved with the Save button in the app toolbar.
See also
- System prompts – steer AI behavior via system instructions
- Models – configure available providers and models
- Tools and integrations (user manual) – explanation of the tools from the user perspective