Skip to content

Commit 2ab0696

Browse files
adriendupuisbarw4
andauthored
Apply suggestions from code review
Co-authored-by: Bartek Wajda <bartlomiej.wajda@ibexa.co> Co-authored-by: Adrien Dupuis <61695653+adriendupuis@users.noreply.github.com>
1 parent 0d5be8f commit 2ab0696

3 files changed

Lines changed: 5 additions & 4 deletions

File tree

docs/ai/mcp/mcp_config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ Install the LTS Update package with Composer:
1616
composer require ibexa/mcp
1717
```
1818

19-
MCP Servers feature doesn't come with a default configuration.
19+
MCP Servers feature comes with [built-in tools](#built-in-tools) but doesn't come with a default configuration.
2020
You have to create your own MCP servers through [their configuration](#mcp-server-configuration)
21-
and [enable JWT athentication for them](#jwt-mcp-firewall).
21+
and [enable JWT authentication for them](#jwt-mcp-firewall).
2222

2323
## Authentication configuration
2424

docs/ai/mcp/mcp_guide.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,8 @@ The MCP servers feature is an [LTS Update package](editions.md#lts-updates) avai
1919
With the MCP servers feature, you can:
2020

2121
- create MCP servers [by using YAML configuration](mcp_config.md#mcp-server-configuration)
22-
- assign different [tools](mcp_config.md#built-in-tools), prompts, and resources to different MCP servers, varying them for each site
22+
- assign different tools, prompts, and resources to different MCP servers, varying them for each site
23+
- assign [built-in tools](mcp_config.md#built-in-tools) included in the package
2324
- [create custom server capabilities](mcp_usage.md#create-capability-class) with PHP API
2425

2526
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ This example introduce an `example` MCP server with a single `greet` tool.
7171
It's enabled on the default repository and all SiteAccesses.
7272
It's accessible with the path `/mcp/example` (for example, on `http://localhost/mcp/example` and `http://localhost/admin/mcp/example`).
7373
It uses files for both discovery cache and session storage.
74-
(Redis/Valkey would probably be better for session storage in production, but file storage is easier for this example and testing.)
74+
(Redis/Valkey would be better for session storage in production, but file storage is easier for this example and testing.)
7575

7676
In a new `config/packages/mcp.yaml` file, define a new MCP server for the `default` repository and assign it to all SiteAccesses:
7777

0 commit comments

Comments
 (0)