Laravel AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_PATH | No | The path to the documentation directory. If not specified, the server expects documentation in a './docs' folder relative to the project root. | ./docs |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_doc_structureB | Get the structure of all available documentation files |
| read_docC | Read a specific documentation file |
| search_docsC | Search for content across all documentation files |
| get_quick_referenceB | Get the quick reference documentation (all coding rules) |
| get_templatesC | Get implementation templates for CRUD operations |
| get_checklistC | Get code validation checklist |
| get_domain_examplesC | Get domain-specific implementation examples |
| get_design_systemC | Get design system documentation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools target different aspects of documentation retrieval: checklists, design systems, structures, examples, references, templates, specific files, and search. There is no overlap in functionality.
All tools follow a consistent verb_noun pattern using snake_case. Each name starts with 'get_' or a similar verb ('read_', 'search_') followed by a descriptive noun, making the set predictable and readable.
With 8 tools, the server is well-scoped for its purpose of providing Laravel documentation and resources. Each tool earns its place by covering a specific aspect of documentation retrieval, avoiding bloat or thinness.
The tool surface is complete for the domain of documentation access, covering all key operations: retrieving specific files, searching, getting structured overviews, examples, templates, and references. There are no obvious gaps that would hinder an agent's workflow.