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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago