Add linebreak to make it readable in IDE

Author: chr-hertel

README.md

@@ -1,13 +1,17 @@
 # MCP PHP SDK
 
-The official PHP SDK for Model Context Protocol (MCP). It provides a framework-agnostic API for implementing MCP servers and clients in PHP.
+The official PHP SDK for Model Context Protocol (MCP). It provides a framework-agnostic API for implementing MCP servers
+and clients in PHP.
 
 > [!IMPORTANT]
-> This SDK is currently in active development with ongoing refinement of its architecture and features. While functional, the API may experience changes as we work toward stabilization.
+> This SDK is currently in active development with ongoing refinement of its architecture and features. While
+> functional, the API may experience changes as we work toward stabilization.
 > 
 > If you want to help us stabilize the SDK, please see the [issue tracker](https://github.com/modelcontextprotocol/php-sdk/issues).
 
-This project represents a collaboration between [the PHP Foundation](https://thephp.foundation/) and the [Symfony project](https://symfony.com/). It adopts development practices and standards from the Symfony project, including [Coding Standards](https://symfony.com/doc/current/contributing/code/standards.html) and the [Backward Compatibility Promise](https://symfony.com/doc/current/contributing/code/bc.html).
+This project represents a collaboration between [the PHP Foundation](https://thephp.foundation/) and the [Symfony project](https://symfony.com/). It adopts
+development practices and standards from the Symfony project, including [Coding Standards](https://symfony.com/doc/current/contributing/code/standards.html) and the
+[Backward Compatibility Promise](https://symfony.com/doc/current/contributing/code/bc.html).
 
 Until the first major release, this SDK is considered [experimental](https://symfony.com/doc/current/contributing/code/experimental.html).
 
@@ -249,11 +253,14 @@ $server = Server::builder()
 
 ## Contributing
 
-We are passionate about supporting contributors of all levels of experience and would love to see you get involved in the project. See the [contributing guide](CONTRIBUTING.md) to get started before you [report issues](https://github.com/modelcontextprotocol/php-sdk/issues) and [send pull requests](https://github.com/modelcontextprotocol/php-sdk/pulls).
+We are passionate about supporting contributors of all levels of experience and would love to see you get involved in
+the project. See the [contributing guide](CONTRIBUTING.md) to get started before you [report issues](https://github.com/modelcontextprotocol/php-sdk/issues) and [send pull requests](https://github.com/modelcontextprotocol/php-sdk/pulls).
 
 ## Credits
 
-The starting point for this SDK was the [PHP-MCP](https://github.com/php-mcp/server) project, initiated by [Kyrian Obikwelu](https://github.com/CodeWithKyrian), and the [Symfony AI initiative](https://github.com/symfony/ai). We are grateful for the work done by both projects and their contributors, which created a solid foundation for this SDK.
+The starting point for this SDK was the [PHP-MCP](https://github.com/php-mcp/server) project, initiated by
+[Kyrian Obikwelu](https://github.com/CodeWithKyrian), and the [Symfony AI initiative](https://github.com/symfony/ai). We are grateful for the work
+done by both projects and their contributors, which created a solid foundation for this SDK.
 
 ## License
 

docs/examples.md

@@ -1,6 +1,7 @@
 # Examples
 
-The MCP PHP SDK includes comprehensive examples demonstrating different patterns and use cases. Each example showcases specific features and can be run independently to understand how the SDK works.
+The MCP PHP SDK includes comprehensive examples demonstrating different patterns and use cases. Each example showcases
+specific features and can be run independently to understand how the SDK works.
 
 ## Table of Contents
 
@@ -13,7 +14,8 @@ The MCP PHP SDK includes comprehensive examples demonstrating different patterns
 
 ## Getting Started
 
-All examples are located in the `examples/` directory and use the SDK dependencies from the root project. Most examples can be run directly without additional setup.
+All examples are located in the `examples/` directory and use the SDK dependencies from the root project. Most examples
+can be run directly without additional setup.
 
 ### Prerequisites
 

docs/mcp-elements.md

@@ -1,6 +1,8 @@
 # MCP Elements
 
-MCP elements are the core capabilities of your server: Tools, Resources, Resource Templates, and Prompts. These elements define what your server can do and how clients can interact with it. The PHP MCP SDK provides both attribute-based discovery and manual registration methods.
+MCP elements are the core capabilities of your server: Tools, Resources, Resource Templates, and Prompts. These elements
+define what your server can do and how clients can interact with it. The PHP MCP SDK provides both attribute-based
+discovery and manual registration methods.
 
 ## Table of Contents
 
@@ -26,7 +28,8 @@ MCP defines four types of capabilities:
 
 Each capability can be registered using two methods:
 
-1. **Attribute-Based Discovery**: Use PHP attributes (`#[McpTool]`, `#[McpResource]`, etc.) on methods or classes. The server automatically discovers and registers them.
+1. **Attribute-Based Discovery**: Use PHP attributes (`#[McpTool]`, `#[McpResource]`, etc.) on methods or classes. The
+   server automatically discovers and registers them.
 
 2. **Manual Registration**: Explicitly register capabilities using `ServerBuilder` methods (`addTool()`, `addResource()`, etc.).
 
@@ -315,7 +318,8 @@ public function getFile(string $path): string
 
 ## Resource Templates
 
-Resource templates are **dynamic resources** that use parameterized URIs with variables. They follow all the same rules as static resources (URI schemas, return values, MIME types, etc.) but accept variables using [RFC 6570 URI template syntax](https://datatracker.ietf.org/doc/html/rfc6570).
+Resource templates are **dynamic resources** that use parameterized URIs with variables. They follow all the same rules
+as static resources (URI schemas, return values, MIME types, etc.) but accept variables using [RFC 6570 URI template syntax](https://datatracker.ietf.org/doc/html/rfc6570).
 
 ```php
 use Mcp\Capability\Attribute\McpResourceTemplate;
@@ -476,7 +480,9 @@ The SDK automatically validates that all messages have valid roles and converts
 
 ## Completion Providers
 
-Completion providers help MCP clients offer auto-completion suggestions for Resource Templates and Prompts. Unlike Tools and static Resources (which can be listed via `tools/list` and `resources/list`), Resource Templates and Prompts have dynamic parameters that benefit from completion hints.
+Completion providers help MCP clients offer auto-completion suggestions for Resource Templates and Prompts. Unlike Tools
+and static Resources (which can be listed via `tools/list` and `resources/list`), Resource Templates and Prompts have
+dynamic parameters that benefit from completion hints.
 
 ### Completion Provider Types
 
@@ -572,11 +578,13 @@ public function getUserProfile(
 
 > **Important**
 > 
-> Completion providers only offer **suggestions** to users. Users can still input any value, so **always validate parameters** in your handlers. Providers don't enforce validation - they're purely for UX improvement.
+> Completion providers only offer **suggestions** to users. Users can still input any value, so **always validate
+> parameters** in your handlers. Providers don't enforce validation - they're purely for UX improvement.
 
 ## Schema Generation and Validation
 
-The SDK automatically generates JSON schemas for **tool parameters** using a sophisticated priority system. Schema generation applies to both attribute-discovered and manually registered tools.
+The SDK automatically generates JSON schemas for **tool parameters** using a sophisticated priority system. Schema
+generation applies to both attribute-discovered and manually registered tools.
 
 ### Schema Generation Priority
 
@@ -682,7 +690,8 @@ public function makeApiRequest(string $endpoint, string $method, array $headers)
 }
 ```
 
-**Warning:** Only use complete schema override if you're well-versed with JSON Schema specification and have complex validation requirements that cannot be achieved through the priority system.
+**Warning:** Only use complete schema override if you're well-versed with JSON Schema specification and have complex
+validation requirements that cannot be achieved through the priority system.
 
 ## Discovery vs Manual Registration
 

docs/server-builder.md

@@ -1,6 +1,8 @@
 # Server Builder
 
-The server `Builder` is a fluent builder class that simplifies the creation and configuration of an MCP server instance. It provides methods for setting server information, configuring discovery, registering capabilities, and customizing various aspects of the server behavior.
+The server `Builder` is a fluent builder class that simplifies the creation and configuration of an MCP server instance.
+It provides methods for setting server information, configuring discovery, registering capabilities, and customizing
+various aspects of the server behavior.
 
 ## Table of Contents
 
@@ -40,7 +42,8 @@ $server = (new Builder())
     ->build();
 ```
 
-Both methods return a `Builder` instance that you can configure with fluent methods. The `build()` method returns the final `Server` instance ready for use.
+Both methods return a `Builder` instance that you can configure with fluent methods. The `build()` method returns the
+final `Server` instance ready for use.
 
 ## Server Configuration
 
@@ -126,7 +129,8 @@ $server = Server::builder()
 - If scanning `lib/` and there's `lib/tests/`, it will be excluded  
 - But if `vendor/` and `tests/` are at the same level as `src/`, they're not scanned anyway (not in `scanDirs`)
 
-> **Performance**: Always use a cache in production. The first run scans and caches all discovered MCP elements, making subsequent server startups nearly instantaneous.
+> **Performance**: Always use a cache in production. The first run scans and caches all discovered MCP elements, making
+> subsequent server startups nearly instantaneous.
 
 ## Session Management
 
@@ -282,15 +286,17 @@ $server = Server::builder()
     );
 ```
 
-**Note:** `name` and `description` are optional for all manual registrations. If not provided, they will be derived from the handler's method name and docblock.
+**Note:** `name` and `description` are optional for all manual registrations. If not provided, they will be derived from
+the handler's method name and docblock.
 
 For more details on MCP elements, handlers, and attribute-based discovery, see [MCP Elements](mcp-elements.md).
 
 ## Service Dependencies
 
 ### Container
 
-The container is used to resolve handlers and their dependencies when handlers inject dependencies in their constructors. The SDK includes a basic container with simple auto-wiring capabilities.
+The container is used to resolve handlers and their dependencies when handlers inject dependencies in their constructors.
+The SDK includes a basic container with simple auto-wiring capabilities.
 
 ```php
 use Mcp\Capability\Registry\Container;
@@ -340,7 +346,8 @@ $server = Server::builder()
 
 ## Custom Capability Handlers
 
-**Advanced customization for specific use cases.** Override the default capability handlers when you need completely custom behavior for how tools are executed, resources are read, or prompts are generated. Most users should stick with the default implementations.
+**Advanced customization for specific use cases.** Override the default capability handlers when you need completely custom
+behavior for how tools are executed, resources are read, or prompts are generated. Most users should stick with the default implementations.
 
 The default handlers work by:
 1. Looking up registered tools/resources/prompts by name/URI
@@ -350,7 +357,8 @@ The default handlers work by:
 
 ### Custom Tool Caller
 
-Replace how tool execution requests are processed. Your custom `ToolCallerInterface` receives a `CallToolRequest` (with tool name and arguments) and must return a `CallToolResult`.
+Replace how tool execution requests are processed. Your custom `ToolCallerInterface` receives a `CallToolRequest` (with
+tool name and arguments) and must return a `CallToolResult`.
 
 ```php
 use Mcp\Capability\Tool\ToolCallerInterface;
@@ -377,7 +385,8 @@ $server = Server::builder()
 
 ### Custom Resource Reader
 
-Replace how resource reading requests are processed. Your custom `ResourceReaderInterface` receives a `ReadResourceRequest` (with URI) and must return a `ReadResourceResult`.
+Replace how resource reading requests are processed. Your custom `ResourceReaderInterface` receives a `ReadResourceRequest`
+(with URI) and must return a `ReadResourceResult`.
 
 ```php
 use Mcp\Capability\Resource\ResourceReaderInterface;
@@ -402,7 +411,8 @@ $server = Server::builder()
 
 ### Custom Prompt Getter
 
-Replace how prompt generation requests are processed. Your custom `PromptGetterInterface` receives a `GetPromptRequest` (with prompt name and arguments) and must return a `GetPromptResult`.
+Replace how prompt generation requests are processed. Your custom `PromptGetterInterface` receives a `GetPromptRequest`
+(with prompt name and arguments) and must return a `GetPromptResult`.
 
 ```php
 use Mcp\Capability\Prompt\PromptGetterInterface;
@@ -426,7 +436,10 @@ $server = Server::builder()
     ->setPromptGetter(new CustomPromptGetter());
 ```
 
-> **Warning**: Custom capability handlers bypass the entire default registration system (discovered attributes, manual registration, container resolution, etc.). You become responsible for all aspect of execution, including error handling, logging, and result formatting. Only use this for very specific advanced use cases like custom authentication, complex routing, or integration with external systems.
+> **Warning**: Custom capability handlers bypass the entire default registration system (discovered attributes, manual
+> registration, container resolution, etc.). You become responsible for all aspect of execution, including error handling,
+> logging, and result formatting. Only use this for very specific advanced use cases like custom authentication, complex
+> routing, or integration with external systems.
 
 ## Complete Example
 

docs/transports.md

@@ -1,6 +1,7 @@
 # Transports
 
-Transports handle the communication layer between MCP servers and clients. The PHP MCP SDK provides two main transport implementations: STDIO for command-line integration and HTTP for web-based communication.
+Transports handle the communication layer between MCP servers and clients. The PHP MCP SDK provides two main transport
+implementations: STDIO for command-line integration and HTTP for web-based communication.
 
 ## Table of Contents
 
@@ -45,7 +46,8 @@ $transport = new StdioTransport(
 - **`logger`** (optional): `LoggerInterface` - PSR-3 logger for debugging. Defaults to `NullLogger`.
 
 > [!IMPORTANT]
-> When using STDIO transport, **never** write to `STDOUT` in your handlers as it's reserved for JSON-RPC communication. Use `STDERR` for debugging instead.
+> When using STDIO transport, **never** write to `STDOUT` in your handlers as it's reserved for JSON-RPC communication.
+> Use `STDERR` for debugging instead.
 
 ### Example Server Script
 
@@ -90,7 +92,8 @@ For MCP clients like Claude Desktop:
 
 ## HTTP Transport
 
-The HTTP transport was designed to sit between any PHP project, regardless of the HTTP implementation or how they receive and process requests and send responses. It provides a flexible architecture that can integrate with any PSR-7 compatible application.
+The HTTP transport was designed to sit between any PHP project, regardless of the HTTP implementation or how they receive
+and process requests and send responses. It provides a flexible architecture that can integrate with any PSR-7 compatible application.
 
 ```php
 use Psr\Http\Message\ServerRequestInterface;
@@ -114,7 +117,8 @@ $transport = new StreamableHttpTransport(
 
 ### Architecture
 
-The HTTP transport doesn't run its own web server. Instead, it processes PSR-7 requests and returns PSR-7 responses that your application can handle however it needs to:
+The HTTP transport doesn't run its own web server. Instead, it processes PSR-7 requests and returns PSR-7 responses that
+your application can handle however it needs to:
 
 ```
 Your Web App → PSR-7 Request → StreamableHttpTransport → PSR-7 Response → Your Web App
@@ -294,7 +298,8 @@ You should route **all methods** to your MCP endpoint, not just POST.
 
 ### Session Management
 
-HTTP transport requires persistent sessions since PHP doesn't maintain state between requests. Unlike STDIO transport where in-memory sessions work fine, HTTP transport needs a persistent session store:
+HTTP transport requires persistent sessions since PHP doesn't maintain state between requests. Unlike STDIO transport
+where in-memory sessions work fine, HTTP transport needs a persistent session store:
 
 ```php
 use Mcp\Server\Session\FileSessionStore;