Laravel Docs MCP Server

Created By
brianirisha year ago
A Model Context Protocl (MCP) server for Laravel Documentation
Overview

What is Laravel Docs MCP Server?

Laravel Docs MCP Server is a Model Context Protocol (MCP) server that provides access to Laravel documentation for AI assistants, language models, and other tools.

How to use Laravel Docs MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, and run the server using Python. You can connect to the server using the FastMCP client library.

Key features of Laravel Docs MCP Server?

  • Lists all available documentation files.
  • Reads specific documentation files.
  • Searches documentation for specific terms.
  • Automatically fetches and updates documentation from Laravel's GitHub repository.
  • Supports different Laravel versions via command line options.

Use cases of Laravel Docs MCP Server?

  1. Enabling AI assistants to provide accurate answers about Laravel.
  2. Facilitating documentation searches for developers.
  3. Keeping documentation up-to-date automatically.

FAQ from Laravel Docs MCP Server?

  • Can this server be used with any version of Laravel?

Yes! The server supports multiple Laravel versions through command line options.

  • Is there a way to update the documentation?

Yes! The server can automatically fetch and update documentation from GitHub.

  • What programming language is used for this project?

The server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brianirish
Star
5
Language
Python
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