Merge branch 'mcp' into mcp-list_non_translated_content_ids

Author: adriendupuis

.github/workflows/code_samples.yaml

@@ -8,8 +8,8 @@ jobs:
         name: Validate code samples
         runs-on: "ubuntu-22.04"
         strategy:
+            fail-fast: false
             matrix:
-                fail-fast: false
                 php:
                     - "8.4" # Upper supported version
                     - "8.3" # Lower supported version

docs/administration/back_office/back_office_configuration.md

@@ -8,7 +8,7 @@ description: Configure default upload locations, pagination limits, and more set
 ## Pagination limits
 
 Default pagination limits for different sections of the back office can be defined through respective settings in
-[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7).
+[`ezplatform_default_settings.yaml`](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/Resources/config/ezplatform_default_settings.yaml#L7).
 
 You can set the pagination limit for user settings under the `ibexa.system.<scope>.pagination_user` [configuration key](configuration.md#configuration-files):
 

docs/administration/back_office/back_office_elements/extending_thumbnails.md

@@ -58,7 +58,7 @@ At this point you can go to the back office and check the results.
 !!! note "Thumbnail mechanism "
 
     This strategy overrides all generated thumbnails. You can specify a specific content type.
-    See the example [here](https://github.com/ibexa/user/blob/main/src/lib/Strategy/DefaultThumbnailStrategy.php)
+    See the example [here](https://github.com/ibexa/user/blob/5.0/src/lib/Strategy/DefaultThumbnailStrategy.php)
 
 
 ## Other fields as thumbnails

docs/administration/back_office/back_office_elements/importing_assets_from_bundle.md

@@ -32,7 +32,7 @@ To import CSS files only, use:
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/encore/ibexa.config.js)
+    For a full example of importing asset configuration, see [`ibexa.config.js`](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/Resources/encore/ibexa.config.js)
 
 To edit existing configuration entries, either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root folder of your project, create an `ibexa.config.manager.js` file:
 
@@ -74,7 +74,7 @@ module.exports = (ibexaConfig, ibexaConfigManager) => {
 
     After you add new files, run `php bin/console cache:clear`.
 
-    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/main/src/bundle/Resources/encore/ibexa.config.manager.js).
+    For a full example of overriding configuration, see [`ibexa.config.manager.js`](https://github.com/ibexa/fieldtype-matrix/blob/5.0/src/bundle/Resources/encore/ibexa.config.manager.js).
 
 To add a new configuration under your own namespace and with its own dependencies, create an `ibexa.webpack.custom.config.js` file that you create either in the bundle's `Resources/encore/` folder, or in the `encore` folder in the root directory of your project, for example:
 

docs/administration/back_office/back_office_tabs/back_office_tabs.md

@@ -64,7 +64,7 @@ You can also influence tab display (for example, order tabs, remove, or modify t
 
 ## Tab groups
 
-You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/main/src/lib/Component/TabsComponent.php).
+You can create new tab groups by using the [`TabsComponent`](https://github.com/ibexa/admin-ui/blob/5.0/src/lib/Component/TabsComponent.php).
 
 To create a tab group, register it as a service:
 

docs/administration/back_office/subitems_list.md

@@ -145,7 +145,7 @@ Optionally, Sub-items module can take a following list of props:
 - **items** _{Array}_ - list of location's sub-items
 - **limit** _{Number}_ - items limit count
 - **offset** _{Number}_ - items limit offset
-- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/main/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
+- **labels** _{Object}_ - list of module labels, see [sub.items.module.js](https://github.com/ibexa/admin-ui/blob/5.0/src/bundle/ui-dev/src/modules/sub-items/sub.items.module.js) for details. Contains definitions for sub components:
     - **subItems** _{Object}_ - list of sub-items module labels
     - **tableView** _{Object}_ - list of table view component labels
     - **tableViewItem** _{Object}_ - list of table item view component labels

docs/administration/project_organization/bundles.md

@@ -11,7 +11,7 @@ You can also reuse the bundles you create in other projects or share them with t
 
 Many [[= product_name =]] functionalities are provided through separate bundles included in the installation.
 You can see the bundles that are automatically installed with [[= product_name =]] in the respective `composer.json` files.
-For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/master/composer.json).
+For example, for [[= product_name_headless =]], see the [JSON file on GitHub](https://github.com/ibexa/headless/blob/5.0/composer.json).
 
 ## Working with bundles
 

docs/ai/mcp/mcp_config.md

@@ -16,9 +16,9 @@ Install the LTS Update package with Composer:
 composer require ibexa/mcp
 ```
 
-MCP Servers feature doesn't come with a default configuration.
+MCP Servers feature comes with [built-in tools](#built-in-tools) but doesn't come with a default configuration.
 You have to create your own MCP servers through [their configuration](#mcp-server-configuration)
-and [enable JWT athentication for them](#jwt-mcp-firewall).
+and [enable JWT authentication for them](#jwt-mcp-firewall).
 
 ## Authentication configuration
 

docs/ai/mcp/mcp_guide.md

@@ -19,7 +19,8 @@ The MCP servers feature is an [LTS Update package](editions.md#lts-updates) avai
 With the MCP servers feature, you can:
 
 - create MCP servers [by using YAML configuration](mcp_config.md#mcp-server-configuration)
-- assign different [tools](mcp_config.md#built-in-tools), prompts, and resources to different MCP servers, varying them for each site
+- assign different tools, prompts, and resources to different MCP servers, varying them for each site
+- assign [built-in tools](mcp_config.md#built-in-tools) included in the package
 - [create custom server capabilities](mcp_usage.md#create-capability-class) with PHP API
 
 MCP servers are configured per [repository](repository_configuration.md) and assigned to [SiteAccesses](siteaccess.md), allowing for flexible configurations adapted to different contexts.

docs/ai/mcp/mcp_usage.md

@@ -71,7 +71,7 @@ This example introduce an `example` MCP server with a single `greet` tool.
 It's enabled on the default repository and all SiteAccesses.
 It's accessible with the path `/mcp/example` (for example, on `http://localhost/mcp/example` and `http://localhost/admin/mcp/example`).
 It uses files for both discovery cache and session storage.
-(Redis/Valkey would probably be better for session storage in production, but file storage is easier for this example and testing.)
+(Redis/Valkey would be better for session storage in production, but file storage is easier for this example and testing.)
 
 In a new `config/packages/mcp.yaml` file, define a new MCP server for the `default` repository and assign it to all SiteAccesses: