> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://knowledge.buildagil.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Buildagil openCDE MCP Server

||| This role is a preview version. Therefore, it may not behave as expected, or the role may still change. For the time being, this role is available only to project administrators.

* [Options](#3-options)
* [Uses](#3-usage)
* [Limitations](#3-limitations)
* [Authentication](#3-authentication)
* [Visibility & Permissions](#3-visibility-permissions)
* [Surroundings](#3-surroundings)
* [Rate Limits](#3-rate-limits)
* [Terms of Use](#3-terms-of-use)

| For general information on the use of artificial intelligence (AI) in buildagil, see the following article: [Artificial Intelligence](/en/article/artificial-intelligence-1xncdyi/).

||| Please note the [Terms of Use](#3-terms-of-use) when using the openCDE MCP Server. In particular, handle content from buildagil responsibly and ensure adequate data protection. Buildagil has no control over the processing of content outside of buildagil (including external AI environments).

### Options
The buildagil openCDE MCP Server enables the use of content in buildagil via artificial intelligence (AI) using the Model Context Protocol (MCP). This allows external AI applications to search for, query, and analyze content using natural language.

The buildagil openCDE MCP Server offers the following features, among others:
* Search for content across projects or within a single project
* View personal tasks
* View project information
* View Tasks & Topics
* Retrieve documents
* Retrieve document metadata
* View meetings
* View milestones
* Retrieve users
* Use links from buildagil

| The range of features is constantly expanding, such as the ability to view links, attachments, meeting minutes, and document versions, as well as to create or edit content.

### Usage
The buildagil openCDE MCP Server can be used with any external AI environments that support the MCP standard. The following describes how to connect to selected environments:
* [Connection to Microsoft Copilot](/en/article/onedrive-storage-optimization-n4ewdy/)
* [Connection with Claude](/en/article/onedrive-storage-optimization-n4ewdy/)
* [Connection to ChatGPT](/en/article/onedrive-storage-optimization-n4ewdy/)

In other AI environments, the connection can be established using the server URL `https://openapi.buildagil.com/mcp`.

| An external AI application can be opened and used directly from buildagil via the AI Assistant. For more information, see the following article: [AI Assistant](/en/article/ki-assistant-174zczu/)

### Limitations
Only documents with a file size of up to 50 MB are supported. For each document, the first 400,000 characters are read so that the data volume is manageable for the AI. Only text is analyzed; images and graphics are not taken into account.

The following document types are supported:
- Documents: PDF, DOCX, DOCM, ODT
- Presentations: PPTX, ODP
- Spreadsheets: XLSX, XLSM, CSV
- Models: IFC
- Emails: EML, MSG
- Text files: TXT, JSON, XML, MD, HTML, HTM

For all unsupported document types (e.g., ONE, DOC, XLS, PPT, DWG, ZIP), the metadata is returned.

### Authentication
Authentication is based on the Microsoft Identity Platform and is performed using the OAuth 2.0 authorization code flow with user-based login. Each login is associated with a single user. For more information on the Authorization Code Flow, see the following article: [Microsoft Identity Platform and the OAuth 2.0 authorization code flow](https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow).

To authenticate with the buildagil openCDE MCP Server, please contact Support and provide a callback URL to receive the client ID and client secret.

### Visibility & Permissions
The same user-based visibility settings and permissions apply to retrieving and modifying content via the buildagil openCDE MCP Server as they do elsewhere on buildagil. Details can be found at [Visibility & Permissions](/en/article/visibility-permissions-1e977ex/).

| Access to buildagil via the buildagil openCDE MCP Server can be restricted on a project-by-project basis. Please contact Support for assistance. This option will be available in the project settings in the near future.

### Surroundings
Only a production environment is available for the buildagil openCDE MCP Server.

### Rate Limits
The buildagil openCDE MCP Server uses user-based, dynamic rate limiting. During periods of high usage, users may be throttled based on their usage.

### Terms of Use
The MCP Server is made available for the purposes described above in accordance with the fair use principle. Roles, data structures, endpoints, and technical or usage-related restrictions may be adjusted or changed as part of ongoing development. Planned and implemented changes will be published in the [News & Updates](https://knowledge.buildagil.com/de/category/neuigkeiten-updates-1q0366c/).

Users of the MCP Server are responsible for the secure storage of their login credentials and tokens, as well as for the secure and proper use of the MCP Server. Security mechanisms, access restrictions, and rate limits must not be circumvented.

Users are also responsible for handling the data received via the MCP Server in a responsible and appropriate manner and for complying at all times with all legal, security, and data protection requirements. Buildagil has no control over the processing of data outside of buildagil (including external AI environments). Users are also responsible for all actions triggered via the MCP Server, regardless of whether these are triggered manually or automatically (including by AI).

In addition, the following applies: [General Terms of Use for buildagil](https://www.buildagil.com/legal/terms).