Laravel Codebase Introspection and Analysis

Created By
capevacea year ago
MCP Server for Laravel Codebase Intelligence and Introspection For AIs to make sense of your codebase, they need to be able to know what's in it. While vector search is a powerful tool for searching through code, it uses a lot of tokens and doesn't even give you the full picture of your codebase for things like views or routes. This package implements a Model Context Protocol (MCP) server for the mateffy/laravel-introspect package, which allows you to introspect your codebase and get structured information about it. 🔍 Let AI query views, routes, classes and models without needing to read through all of the code 🔍 Can even use wildcards (*) to match multiple views, routes, classes and models 🔍 Supports querying for things from Laravel packages, which most file searchers can't do 🪄 Gives your AI quick overviews of your datamodel and its relationships 🤖 Supports any AI agent implementing the MCP protocol Views: name, path, used by view, uses view, extends Routes: name, URI, controller + fn, methods, middleware Classes: name / namespace, extends parent, implements interfaces, uses traits ⤷ Models: ... relationships, properties, casts, fillable, hidden, read/writeable ⤷ Commands: ... signature, description (coming soon) Name and a few other queries even support wildcard queries (e.g. components.*.paragraph)
Overview

MCP Server for Laravel Codebase Intelligence and Introspection

For AIs to make sense of your codebase, they need to be able to know what's in it. While vector search is a powerful tool for searching through code, it uses a lot of tokens and doesn't even give you the full picture of your codebase for things like views or routes. This package implements a Model Context Protocol (MCP) server for the mateffy/laravel-introspect package, which allows you to introspect your codebase and get structured information about it.

  • 🔍 Let AI query views, routes, classes and models without needing to read through all of the code
  • 🔍 Can even use wildcards (*) to match multiple views, routes, classes and models
  • 🔍 Supports querying for things from Laravel packages, which most file searchers can't do
  • 🪄 Gives your AI quick overviews of your datamodel and its relationships
  • 🤖 Supports any AI agent implementing the MCP protocol

Server Config

{
  "mcpServers": {
    "laravel-introspect": {
      "command": "php",
      "args": [
        "/path/to/your/codebase/artisan",
        "introspect:mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
capevace
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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.

a day ago