AI Integration and Policy Settings
Manage the ways external systems call AI, including external tool API keys and MCP servers.
The installation and connection of the AI model itself is configured first under AI Model Settings. This document explains how to decide where and under what policy the configured AI model is used.
External Tool API Key Management
Manage the connection information used for tasks such as external knowledge collection.

Currently, you can register external tool keys for Google, Naver, and KIPRIS, and additional integration targets may be added over time.
| Item | Description |
|---|---|
| Used for Google-based features such as web search and external information lookup. | |
| Naver | Used for domestic search or Naver-based external lookup features. |
| KIPRIS | Used for intellectual property search features such as patents and trademarks. |
| Custom | Support planned for the future |
If a needed external tool isn't available yet, you can request integration through the feature suggestion channel. The suggestion link may be provided via the common link management document or according to service operation policy.
MCP Server Management
An MCP server is a server that lets external AI clients such as Codex and Claude Code call workspace features—files, search, team activity, and more—in a standardized way. Because there is a lot to configure, such as organization-wide allowed scope settings and per-user key issuance, this is covered in the following document.