feat: mcp support

Author: binaryk

composer.json

@@ -18,9 +18,10 @@
         }
     ],
     "require": {
-        "php": "^8.2",
+        "php": "^8.2|^8.3",
         "illuminate/contracts": "^11.0|^12.0",
         "laravel/pint": "^1.0",
+        "laravel/mcp": "^0.1.0",
         "spatie/laravel-data": "^4.4",
         "spatie/laravel-package-tools": "^1.12",
         "spatie/once": "^3.0"

config/restify.php

@@ -175,4 +175,42 @@
         */
         'max_tokens' => 1000,
     ],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Model Context Protocol (MCP)
+    |--------------------------------------------------------------------------
+    |
+    | These settings control the MCP integration that allows AI agents to
+    | interact with your Restify repositories through structured tool interfaces.
+    |
+    */
+    'mcp' => [
+        'tools' => [
+            'exclude' => [
+                // Tool classes to exclude from discovery
+                // 'App\MCP\Tools\SensitiveTool',
+            ],
+            'include' => [
+                // Additional tool classes to include
+                // 'App\MCP\Tools\CustomTool',
+            ],
+        ],
+        'resources' => [
+            'exclude' => [
+                // Resource classes to exclude from discovery
+            ],
+            'include' => [
+                // Additional resource classes to include
+            ],
+        ],
+        'prompts' => [
+            'exclude' => [
+                // Prompt classes to exclude from discovery
+            ],
+            'include' => [
+                // Additional prompt classes to include
+            ],
+        ],
+    ],
 ];

docs-v2/content/en/api/fields.md

@@ -407,6 +407,49 @@ However, you can populate the field value when the entity is stored by using `va
 Field::new('token')->value(Str::random(32))->hidden();
 ```
 
+### MCP Visibility Control
+
+When using Laravel Restify with Model Context Protocol (MCP), you can control field visibility specifically for MCP requests using dedicated methods:
+
+```php
+// Hide field from MCP requests completely
+Field::new('secret_key')->hideFromMcp()
+
+// Show field only in MCP requests (hide from regular API)
+Field::new('mcp_metadata')->showOnIndex(false)->showOnShow(false)->showOnMcp(true)
+
+// Conditionally hide based on user permissions
+Field::new('admin_notes')->hideFromMcp(function($request, $repository) {
+    return !$request->user()->isAdmin();
+})
+
+// Show field in MCP based on user role
+Field::new('sensitive_data')->showOnMcp(function($request, $repository) {
+    return $request->user()->can('view-sensitive', $repository);
+})
+```
+
+#### MCP Visibility Methods
+
+- **`showOnMcp($callback = true)`** - Control whether the field should be visible in MCP requests
+- **`hideFromMcp($callback = true)`** - Hide the field from MCP requests (inverse of showOnMcp)
+
+Both methods accept either a boolean value or a callback function that receives the request and repository as parameters.
+
+<alert type="info">
+MCP visibility rules take precedence over regular `showOnIndex`/`showOnShow` rules when processing MCP requests. Fields are visible in MCP by default unless explicitly hidden.
+</alert>
+
+#### How It Works
+
+The MCP visibility system automatically detects when a request is coming from an MCP tool and applies the appropriate visibility rules:
+
+1. **Regular API requests** use `showOnIndex()` and `showOnShow()` rules
+2. **MCP requests** use `showOnMcp()` and `hideFromMcp()` rules
+3. **Default behavior** - fields are visible in MCP unless explicitly hidden
+
+This allows you to have different field visibility for your regular API consumers versus AI agents accessing your data through MCP tools.
+
 ## Hooks
 
 ### After store