mattiasgeniar/filament-mcp
Expose your Filament resources to AI agents over MCP. Per-record create, read, and update tools are generated from your existing resource forms; delete tools are opt-in. Access is forbidden by default, gated by a token and your own authorization callback, and every call is audited.
view page (no index/manage) now generates a get_* tool, so single records are fetchable by id without exposing a full listing. list_* still requires an index or manage page. describe_resources now reports a distinct list operation alongside read.config('filament-mcp.server.name'); tabs are collapsed until clicked. Hide it with ui.show_setup_guide => false.$hidden / $visible settings are enforced before MCP schemas are built, excluding hidden attributes from discovery, writes, reads, search, filters, and sorting.user_id token column can upgrade to morph-token storage and still issue new tokens.FilamentMcpPlugin that adds an MCP token page to a panel, where each user generates and revokes their own personal tokens (gated by the same authorization rule as the server).->numeric(), ->integer()) are exposed as JSON Schema number/integer instead of strings.composer require, so php artisan migrate is all that is needed.list, get, create, update, delete) per configured Filament resource.filament-mcp:token command.useFilamentMcp gate or FilamentMcp::authorizeUsing() callback.PreparesRecordData contract.$hidden are dropped from read output.list_* tools support search, field filters, sorting, and pagination.actions config and the ResourceAction base class. Actions are policy-gated (ability(), default update) and only arguments declared in rules() reach the handler.describe_resources discovery tool that maps the exposed resources, operations, actions, and fields.read_fields config option to declare readable fields explicitly for resources whose view schema lives on a page.How can I help you explore Laravel packages today?