Filament MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| filament_get_componentC | Get detailed information about a Filament component |
| filament_list_componentsC | List all components in a category |
| filament_get_namespaceC | Get the correct namespace for a Filament class |
| filament_generate_planD | Generate a Filament implementation plan |
| filament_get_commandsB | Get Filament artisan commands |
| filament_get_relationshipsB | Get Laravel relationship types |
| filament_get_docsC | Fetch documentation from filamentphp.com |
| filament_list_docsC | List documentation sections |
| filament_discover_docsC | Discover live documentation routes from filamentphp.com |
| filament_search_docsC | Search Filament docs and return exact section matches |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_resource_plan | Generate implementation plan for a Filament resource |
| debug_filament_issue | Help debug a Filament issue |
| create_relation_manager | Generate a Filament relation manager |
| create_custom_action | Generate a custom Filament action |
| migrate_to_v5 | Help migrate Filament v4 code to v5 |
| create_form_with_validation | Generate a form with validation |
| create_table_with_features | Generate a table with filters and actions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| filament-v4-components | |
| filament-v5-components | |
| filament-v4-commands | |
| filament-v5-commands | |
| filament-v4-docs-index | |
| filament-v5-docs-index | |
| filament-quick-reference |
TDQS
Scored across 10 tools
Most tools have distinct purposes, such as discovering docs, generating plans, getting commands, and fetching components. However, there is some overlap between filament_discover_docs, filament_get_docs, filament_list_docs, and filament_search_docs, which all relate to documentation access and could cause confusion about which to use for specific queries.
All tool names follow a consistent snake_case pattern with the prefix 'filament_' and a clear verb_noun structure, such as filament_get_component and filament_list_components. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
With 10 tools, the server is well-scoped for assisting with Filament PHP development, covering key areas like documentation, components, commands, and planning. Each tool appears to serve a specific function without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for Filament development tasks, including documentation retrieval, component management, and implementation planning. A minor gap is the lack of tools for creating or modifying Filament resources, such as generating code or updating components, which might limit full lifecycle support.