This release is a pre-release and may not be stable for production use.
Laravel MCP Companion
Every Laravel version, the whole ecosystem, fully local.
Laravel MCP Companion is an MCP server that keeps Laravel's documentation on your machine and lets an AI assistant search and read it. It holds the framework docs for every version from 6.x to the newest, the first-party services, and widely used packages. No documentation is fetched while you work, so it answers without a network connection.
Status: pre-1.0. The tools listed below, with their arguments and results, are the ones 1.0 will promise not to break. Upgrading from 0.14 or earlier? See MIGRATING.md.
What it is for
- Every version, side by side. Laravel 6.x through 13.x are all held. Ask about the version an older application runs on, or compare two versions to see what an upgrade brings.
- Fully local. The documentation ships inside the Docker image and the Python package. Your questions go nowhere but your assistant, and no documentation service is called, so it works offline and behind an air gap. Documentation is fetched only when you ask for an update. The one other request is at startup: if its list of Laravel versions is more than a day old, the server asks GitHub for it, and carries on with the list it has when there is no answer.
- It needs no project. It works in a chat client with no code open.
Laravel Boost is the first-party tool for writing code inside a Laravel project: it is installed into the application and knows what the application uses. Use Boost while building. Use Companion to look something up in any Laravel version, in a client with no project open, or where the documentation has to stay on the machine.
Documentation held
- The framework documentation for Laravel 6.x through 13.x.
- First-party services: Forge, Vapor, Envoyer, Nova, Cloud, Nightwatch and Herd.
- Package documentation: Livewire, Filament, Inertia, and Spatie's Permission, Media Library and Backup, each for the package's current major version, and the smaller docs of Debugbar and IDE Helper.
- Learning material: the courses at laravel.com/learn and an index of Laracasts topics.
- A package catalog. Separate from the documentation above: a hand-written list of 42 curated packages, saying what each is for, how to install it, what goes with it, and which ones have been superseded.
The project refetches the documentation every night and publishes it;
Keeping the documentation current says how it reaches you.
The catalog is revised by hand. Ask your assistant how current its documentation is, or call
laravel_docs_info, to see the date and page count of every source.
Installation
Run it with uvx or with
Docker, whichever you already have. Both carry the
documentation with them. The server is on PyPI
and in the
official MCP Registry
as io.github.brianirish/laravel-mcp-companion.
Cursor and VS Code add it from a link, using uvx. Each shows the configuration before
it installs anything.
Claude Code:
# with uv
claude mcp add laravel-mcp-companion -- uvx laravel-mcp-companion
# with Docker
claude mcp add laravel-mcp-companion -- docker run --rm -i ghcr.io/brianirish/laravel-mcp-companion:latest
Claude Desktop, and most other MCP clients: add one of these to the client's MCP configuration (Settings → Developer → Edit Config in Claude Desktop), then restart it.
With uv:
{
"mcpServers": {
"laravel-mcp-companion": {
"command": "uvx",
"args": ["laravel-mcp-companion"]
}
}
}
With Docker:
{
"mcpServers": {
"laravel-mcp-companion": {
"command": "docker",
"args": ["run", "--rm", "-i", "ghcr.io/brianirish/laravel-mcp-companion:latest"]
}
}
}
pip install laravel-mcp-companion works too, on Python 3.12 or newer, and installs a
laravel-mcp-companion command.
Then ask your assistant "how current are your Laravel docs?". It should answer with a date and a list of sources.
Features (v1.0.0-rc1)
Twelve tools. API.md documents every argument and result field.
| Tool | What it does |
|---|---|
search_laravel_docs |
Ranked search over everything held; returns sections, each with a snippet |
read_laravel_doc_section |
Reads one section of a page |
read_laravel_doc_content |
Reads a whole page, or lists its headings |
list_laravel_docs |
Lists what is held, or the files of one collection |
laravel_docs_info |
Reports how current every source is |
compare_laravel_versions |
Lists the pages one Laravel version has and another lacks |
update_laravel_docs |
Fetches newer documentation |
get_laravel_package |
Looks up a package, or a category, in the catalog |
recommend_laravel_packages |
Suggests packages for a described need |
get_laravel_service_info |
Describes a first-party service and what is held for it |
get_laravel_learning_path |
Returns a reading order for a goal (experimental) |
browse_docs_by_category |
Lists pages by topic and difficulty (experimental) |
- Ranked sections, not files. Ask in plain language ("how do I retry a failed queue job") and get the sections that answer it. A section is usually a few hundred tokens where the whole page is tens of thousands.
- Unified search - One search covers the core framework docs, the services, the package docs
and the learning resources, and labels each result with its source.
sourcesnarrows it. - Results a program can use. Every tool returns a JSON object matching a declared schema, as
well as text for the model. A failure is an error with a
codeto branch on. - A stable surface. The tools are recorded in a contract file that a test enforces. VERSIONING.md says what 1.0 will promise; the two tools marked experimental are outside it.
By default a client is shown four tools, not twelve: the first two above, and two helpers that
find and run the rest. That keeps tool descriptions out of the model's context.
--transform-mode none lists all twelve; see
Tool listing modes.
Keeping the documentation current
The project refetches every source each night.
-
Docker: each night's documentation is published as a new image. Pull it:
docker pull ghcr.io/brianirish/laravel-mcp-companion:latest
-
uvxorpip: the package carries the documentation as it was on its release date, and the nightly documentation is not published to PyPI. Ask your assistant to update its Laravel docs and the server fetches them from their sources. The update is kept in a directory of your own, so it outlasts an upgrade.
Asking the assistant works with Docker too, but a container started with --rm loses the update
when it stops. OPERATIONS.md covers image
tags, keeping fetched documentation in a Docker volume, and where a pip or uvx install
stores it.
More
| OPERATIONS.md | Every option, tool listing modes, running over HTTP with authentication and rate limiting, health and metrics, the output format |
| API.md | Every tool, argument, result field and error code |
| MIGRATING.md | Upgrading from 0.14 or earlier |
| VERSIONING.md | What a version number promises |
| ROADMAP.md | What is left before 1.0 |
| CONTRIBUTING.md | Development setup and tests |
| SECURITY.md | Reporting a vulnerability |
License
MIT. See LICENSE.
Acknowledgements
- Laravel for their excellent documentation
- Laravel package authors for their contributions to the ecosystem
Metadata
Release files for laravel-mcp-companion 1.0.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| laravel_mcp_companion-1.0.0rc1.tar.gz | 6.7 MB | With provenance | Details for laravel_mcp_companion-1.0.0rc1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| laravel_mcp_companion-1.0.0rc1-py3-none-any.whl | Python 3 | none | any | Details for laravel_mcp_companion-1.0.0rc1-py3-none-any.whl |
Total release size: 14.6 MB
Release files / laravel_mcp_companion-1.0.0rc1.tar.gz
| Download URL | laravel_mcp_companion-1.0.0rc1.tar.gz |
|---|---|
| Size | 6.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea2bc549abe925d0036916eafe8aa248ff70bfa285c60b21d1d535a0250ad7cc
|
|
BLAKE2b-256 checksum How to use checksums |
4bc183e553da0e6308db283d468ad0b5f97c201b9c5364afa04e608d67d580f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / laravel_mcp_companion-1.0.0rc1-py3-none-any.whl
| Download URL | laravel_mcp_companion-1.0.0rc1-py3-none-any.whl |
|---|---|
| Size | 7.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ff7dfdfade274cf3b698c014da4134228849f5c6689354d8c50703fee5e63d35
|
|
BLAKE2b-256 checksum How to use checksums |
8a4bff6403ad419c13f921035d9d5630d9f64ae193603b6b6aa77dc905202a93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for laravel-mcp-companion 1.0.0rc1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for laravel_mcp_companion-1.0.0rc1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.