Weave Code
Filament Mcp Laravel Package
guava/filament-mcp
guava/filament-mcp brings the Model Context Protocol to Filament, exposing your admin panel's resources and tools to AI assistants and MCP clients so they can query and act on your Laravel app through a standardized, permission-aware interface.
Give your Filament panels MCP capabilities. Expose resources, records and actions to AI agents - configurable and secure.
Frequently asked questions about Filament Mcp
- How do I install guava/filament-mcp in a Laravel app?
- Installation is expected to follow the usual Laravel package flow: composer require guava/filament-mcp, register the Filament plugin on a panel, and publish the config file. The repository is at an early 1.0.0 release with a single commit, so confirm the exact commands and plugin registration API in the package source before wiring it into an app. Run composer require guava/filament-mcp --dry-run first to surface dependency conflicts.
- Which Laravel, PHP, and Filament versions does guava/filament-mcp support?
- The declared PHP, Laravel, and Filament constraints are not verified from the release information provided, so do not assume support for a specific major. Check the package's composer.json and run a dry-run install against your locked dependency set. The assessment treats Laravel 11 or 12, Filament 3 or 4, and PHP 8.2+ as a hypothesis to validate, not a confirmed support matrix.
- Which MCP transports does filament-mcp support?
- Supported transports are not documented in the available information, and this is one of the key unknowns to verify. Confirm whether the package exposes a stdio command, an HTTP or SSE endpoint, or both. If an HTTP surface exists, check whether authentication is enabled by default or must be opted into.
- Does guava/filament-mcp respect Filament policies and tenant scoping?
- The authorization model is the most important unknown: verify whether tool invocations re-enter Filament policies, canAccessPanel checks, and tenant scoping. Do not assume that exposing a resource as an MCP tool automatically inherits the same access rules as the admin UI. Test with users from different roles and tenants before trusting it.
- Can I run filament-mcp in read-only mode?
- It is not confirmed whether generated tools are read-only or include create, update, and delete actions. Check the package for a global read-only mode and inspect exactly which Filament actions become callable. For an initial evaluation, prefer a read-only configuration if the package supports one.
- Is guava/filament-mcp safe for production use?
- Treat production use as high risk until the authorization, transport authentication, and write-tool behavior are proven. MCP tools that expose admin data are an exfiltration path, and prompt injection through content reaching an agent with admin tools is a live threat model. Validate on a non-production panel first and confirm whether rate limiting, audit logging, and per-token scoping exist.
- How do I connect Claude Desktop or Cursor to my Filament panel with MCP?
- MCP-capable clients such as Claude Desktop, Cursor, and IDE agents can discover and invoke panel capabilities exposed by the package. The exact endpoint or command configuration and the supported MCP spec revision are unverified, so match them against what your chosen client implements. Start with a minimal panel and a read-only tool set before broadening access.
- How should I test filament-mcp before exposing a production panel?
- There is no evidence in the provided assessment of test coverage or a CI matrix across Filament majors. Build a spike that exercises a fresh panel and a panel with custom resources and relation managers. Confirm tool discovery, authorization behavior, and error handling in a non-production environment before rollout.
- What are alternatives to guava/filament-mcp?
- A bespoke tool-calling API or an existing read-only API is the natural comparison point, because this package aims to replace that custom glue with a standardized MCP interface. No specific alternative packages are identified in the provided context, so compare candidates on transport support, authorization depth, and Filament version tracking. The main trade-off is convenience versus the maturity and security unknowns of an early 1.0.0 release.
- How stable and actively maintained is guava/filament-mcp?
- The package is at 1.0.0 with a single initial commit, no changelog, no migration guide, and no documented backwards-compatibility policy. GuavaCZ maintains a broad portfolio of Filament plugins, so maintenance bandwidth is a consideration. Pin exact version 1.0.0 for the first evaluation cycle rather than a caret range, and expect possible breaking changes in 1.x.
Weaver
How can I help you explore Laravel packages today?