Download the PHP package neo4j/laravel-boost without Composer
On this page you can find all versions of the php package neo4j/laravel-boost. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download neo4j/laravel-boost
More information about neo4j/laravel-boost
Files in neo4j/laravel-boost
Package laravel-boost
Short Description Official Neo4j MCP server integration for Laravel
License MIT
Informations about the package laravel-boost
and **see how your whole Laravel app is wired together**: routes, jobs, events, policies, and every dependency behind them. [](https://packagist.org/packages/neo4j/laravel-boost) [](https://www.php.net/) [](https://laravel.com/) [](https://packagist.org/packages/neo4j/laravel-boost) [](https://github.com/neo4j-php/neo4j-boost/actions/workflows/phpunit.yml) [](https://github.com/neo4j-php/neo4j-boost/actions/workflows/phpstan.yml) [](https://github.com/neo4j-php/neo4j-boost/actions/workflows/pint.yml) **[Quick Start](#5-minute-quick-start)** · **[Container Graph](#exploring-your-container-dependency-graph)** · **[Prompts](docs/PROMPTS.md)** · **[Troubleshooting](docs/TROUBLESHOOTING.md)** · **[Changelog](CHANGELOG.md)**
Your Laravel app, as a graph your AI can walk.
Ask your app questions it could never answer before
💬 "What does my Neo4j schema look like?" → the assistant runs
get-schemaagainst your live database, not a guess from your code.💬 "Which classes end up being built when
POST /checkoutis hit?" → it walks route → controller → every dependency in the container graph.💬 "Which queued jobs use the
redisconnection, and what do they depend on?" → one graph query instead of an afternoon of grepping.💬 "What breaks if I change
PaymentGateway?" →get-class-dependency-graphshows everything that depends on it, inbound and outbound.
More ready-to-paste prompts: docs/PROMPTS.md.
Why you'll love it
| ### 🔌 One MCP entry Neo4j tools ride on your existing **Laravel Boost** server (`php artisan boost:mcp`). No second server to wire up. | ### ⚡ Zero binaries The default **driver** transport talks Bolt straight from PHP. Nothing to download, nothing to keep running. | ### 🕸️ Your app as a graph `container:graph` exports routes, middleware, jobs, events, policies, mail, notifications, broadcasting, and container wiring into Neo4j. |
| ### 🧠 Live schema & Cypher `get-schema`, `read-cypher`, and `write-cypher` work against your real database from any MCP client. | ### 🩺 Built-in doctor `neo4j-boost:doctor` checks transport, credentials, and connectivity, then tells you exactly what's wrong. | ### 🐳 Neo4j in one command `neo4j-boost:start-neo4j` boots a local Docker Neo4j with APOC ready to go. |
Works with Cursor, Claude Code, and any other MCP-compatible client.
How it works
The assistant gets these tools next to your usual Boost tools:
| Tool | What your assistant can do with it |
|---|---|
get-schema |
See the labels, relationships, and properties in your live database |
read-cypher |
Run read-only Cypher queries |
write-cypher |
Create and update data |
get-class-dependency-graph |
Trace what a class depends on, and what depends on it |
contribute-graph-knowledge |
Record wiring it discovered so the graph gets smarter |
list-gds-procedures |
Discover Graph Data Science algorithms (needs the GDS plugin) |
Architecture deep dive: What is Neo4j Boost?
Installation
Requirements: PHP 8.2+ and Laravel 12 or 13.
1. Install the package
2. Add your Neo4j credentials
The default driver transport runs the Neo4j tools in PHP over Bolt (via laudis/neo4j-php-client), so no neo4j-mcp binary is needed:
[!TIP]
NEO4J_MCP_TRANSPORTdefaults todriver. You can switch tostdio(runs theneo4j-mcpbinary) orhttp(remote MCP server). See Troubleshooting.
3. Run the interactive setup
It checks your connection, can install the neo4j-mcp binary, and can start a local Neo4j in Docker.
4. No Neo4j yet? Start one
This starts Neo4j in Docker on bolt://localhost:7687 and http://localhost:7474, with the APOC plugins the schema tools need. If it doesn't come up, see Docker setup troubleshooting.
5-minute Quick Start
Connect your MCP client and you're done. In every client, the server entry is the same:
Cursor
Add the entry above to .cursor/mcp.json in your project root, or let the package write it for you:
Open your Laravel application folder as the workspace, reload MCP settings, and enable the server. get-schema, read-cypher, and write-cypher appear next to your Boost tools.
Connect the tools |
Ask for the schema |
Read with Cypher |
Write with Cypher |
Claude Code
Add the entry to claude_code_config.json (or run claude mcp add with the same definition). Open your Laravel application folder as the workspace so artisan is reachable.
Now ask: "What does my Neo4j schema look like?" Your assistant should answer using get-schema against your live database.
[!NOTE] Wrong workspace, missing
APP_ENV=local, or HTTP/mcp404s? See MCP configuration troubleshooting.
Exploring Your Container Dependency Graph
This is the superpower. One command exports how your Laravel app is actually wired at runtime into Neo4j:
What ends up in the graph:
:Abstract is the container lookup key (the same idea as make($abstract)), with a kind property (Class / Interface / AbstractType). Bindings use BINDS_TO between abstracts.
Then ask your assistant, or call get-class-dependency-graph directly:
🔍 Ready-made Neo4j Browser queries (routes, jobs, scheduled tasks, auth, policies, gates, notifications, mail, broadcasting, Artisan commands, service providers, model events)
**Routes and their middleware** **Jobs, their queue connection, and dependencies** **Scheduled tasks** **Auth guards, providers, and models** **Policies** **Gate abilities** **Notifications and channels** **Mailables, mailers, and queue connections** **Broadcast channels** **Artisan commands** **Service providers** **Eloquent model events**
🕵️ Find hidden dependencies with static scanning
Runtime reflection can't see service-location calls, facade usage, or direct `new` instantiations. Point the static scanner at your app directories to catch them: You can also publish the config and set `container_graph.static_scan_paths`. If unset, no PHP files are scanned and only runtime reflection edges are exported.
[!NOTE] The export maps every PSR-4 class in the container. On apps with hundreds of services it takes a little while and produces a big graph. That's expected.
Available Artisan Commands
| Command | What it does |
|---|---|
neo4j-boost:setup |
Interactive setup: checks the connection, can configure Docker Neo4j, writes Cursor config |
neo4j-boost:start-neo4j |
Starts a local Neo4j Docker instance |
neo4j-boost:cursor-config |
Creates or updates .cursor/mcp.json |
neo4j-boost:install-mcp |
Downloads the official neo4j-mcp binary (only needed for STDIO) |
neo4j-boost:doctor |
Diagnoses transport, binary, password, and overall readiness |
neo4j-boost:test-stdio |
Verbose end-to-end test of the STDIO handshake and tools |
container:graph |
Exports routes, middleware, events, jobs, queue connections, scheduled tasks, auth config, policies, gates, notifications, mail, broadcasting, and container wiring into Neo4j (--dry-run, --print-cypher) |
Configuration
Transport Modes
| Mode | How it connects | When to use it |
|---|---|---|
driver (default) |
PHP talks to Neo4j over Bolt via laudis/neo4j-php-client |
Almost always. No binary needed |
stdio |
Runs the official neo4j-mcp binary as a subprocess |
You want the official binary. Install it with php artisan neo4j-boost:install-mcp, then set NEO4J_MCP_TRANSPORT=stdio |
http |
Calls a remote or containerized MCP server | Set NEO4J_MCP_TRANSPORT=http and NEO4J_MCP_URL=http://localhost:8080/mcp |
[!IMPORTANT] In HTTP mode this package sends your Neo4j credentials with every request, so don't set
NEO4J_USERNAMEorNEO4J_PASSWORDon the MCP server container itself.
Run php artisan config:clear after editing .env. Auth and env mistakes are covered in Environment configuration.
Neo4j Aura? Use the Aura console URI (neo4j+s://...) with driver transport. See Neo4j Aura connectivity.
Using Docker Compose (HTTP mode)
🐳 Show the docker-compose.yml
Then point Laravel at it: Networking, plugin, and port issues: [Docker setup troubleshooting](docs/TROUBLESHOOTING.md#docker-setup).
Graph Data Science (GDS) Plugin
list-gds-procedures needs the Graph Data Science plugin. Without it, only that tool errors; get-schema, read-cypher, and write-cypher keep working. With Docker, add NEO4J_PLUGINS: '["apoc", "graph-data-science"]' and the NEO4J_dbms_security_procedures_* variables shown above.
⚙️ More options: publishing config, running setup after updates, binary platforms
**Publish the config** to tweak `neo4j_mcp.transport`, `bolt.uri`, `bolt.username`, `http.url`, and more in `config/neo4j-boost.php`: **Re-run setup after every `composer update`:** **Binary platforms** (`neo4j-boost:install-mcp`): Linux (x86_64, arm64, i386), macOS (x86_64, Apple Silicon), and Windows (x86_64, arm64, i386). Windows uses `.zip` archives (needs `ext-zip`); Linux and macOS use `.tar.gz`. If detection fails, set `NEO4J_MCP_PLATFORM_ASSET` in `.env`.
Common Issues & Troubleshooting
Something off? Start here, especially after any .env change (then php artisan config:clear):
| Symptom | Fix |
|---|---|
Could not open input file: artisan |
Open your Laravel app folder as the workspace, not the package folder. More |
There are no commands defined in the "boost" namespace |
Add "env": { "APP_ENV": "local" } to your MCP server entry |
STDIO: Neo4j password is required |
Set NEO4J_PASSWORD in .env, then php artisan config:clear. More |
| APOC / meta errors | Recreate local Neo4j: php artisan neo4j-boost:start-neo4j --recreate. More |
Docker: can't reach bolt://localhost:7687 |
When Laravel isn't on the host, use the Neo4j service hostname on the container network, then clear config cache |
HTTP 404 This server only handles requests to /mcp |
Prefer Laravel Boost (php artisan boost:mcp). Connecting directly? Make sure the URL ends in /mcp and HTTP transport is on |
Unknown function 'gds.version' |
Install the GDS plugin. Schema and Cypher tools still work without it |
| Aura connection failures | Use the Aura console URI (neo4j+s://...) with driver transport. More |
The full step-by-step guide (Docker, Aura, MCP, auth, environment, error messages) lives in docs/TROUBLESHOOTING.md.
Learn more
| 📖 What is Neo4j Boost? | The big picture, in plain words |
| 🚀 Getting started | Step-by-step first run |
| 🕸️ Container graph tutorial | Everything container:graph can do |
| 💬 Prompt library | Copy-paste prompts for common workflows |
| 🏗️ Architecture | Components, MCP, and request flow |
| 🎬 Demo media | All the GIFs and how they were made |
| 📝 Changelog | What changed in each release |
Maintained by [Nagels Tech](https://nagels.tech/)
All versions of laravel-boost with dependencies
laravel/framework Version ^12.0|^13.0
laravel/boost Version ^2.0
laudis/neo4j-php-client Version ^3.4