Filament MCP Server - Laravel Loop

Created By
kirschbaum-developmenta year ago
Filament MCP Server for Laravel Loop
Overview

What is Laravel Loop Filament?

Laravel Loop Filament is an extension for Laravel Loop that exposes Filament Resources as an MCP server, allowing AI assistants and MCP clients to interact with these resources for data listing, querying, and executing actions.

How to use Laravel Loop Filament?

To use Laravel Loop Filament, first ensure Laravel Loop is installed. Then, install the package via Composer and register the Filament toolkit in your application. Connect Laravel Loop to an MCP client to access the tools.

Key features of Laravel Loop Filament?

  • Exposes Filament Resources as MCP tools.
  • Four available tools: list resources, describe resource structure, query resource data, and execute bulk actions.
  • Supports both read-only and read-write modes for resource actions.

Use cases of Laravel Loop Filament?

  1. Listing all available Filament Resources for an MCP client.
  2. Describing the structure and fields of a specific resource.
  3. Querying data with optional filters for specific resources.
  4. Executing bulk actions on resources in ReadWrite mode.

FAQ from Laravel Loop Filament?

  • Is this project stable for production use?

No, this is a beta version and is not recommended for production use yet.

  • What is the license for this project?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kirschbaum-development
Star
7
Language
PHP
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago