Laravel Loop

Created By
kirschbaum-developmenta year ago
Laravel Loop is a powerful Model Context Protocol (MCP) server designed specifically for Laravel applications. It connects your Laravel application with AI assistants using the MCP protocol.
Overview

What is Laravel Loop?

Laravel Loop is a powerful Model Context Protocol (MCP) server designed specifically for Laravel applications. It connects your Laravel application with AI assistants using the MCP protocol.

How to use Laravel Loop?

To use Laravel Loop, install the package via composer and publish the configuration file. Then, register your tools in the AppServiceProvider and connect your MCP client to the Laravel Loop MCP server.

Key features of Laravel Loop?

  • Create and expose your own tools integrated with Laravel applications.
  • Connect with various MCP clients like Claude Code, Cursor, and Windsurf.
  • Pre-built tools for interacting with models and APIs, such as Stripe.

Use cases of Laravel Loop?

  1. Building custom tools for Laravel applications.
  2. Integrating AI assistants with Laravel applications.
  3. Interacting with external APIs like Stripe.

FAQ from Laravel Loop?

  • Is Laravel Loop stable?

Laravel Loop is currently in beta and still under development.

  • How do I connect my MCP client?

You can connect your MCP client using the provided artisan commands and configuration options.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kirschbaum-development
Star
61
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)

2 days ago