Download the PHP package routewise/laravel without Composer

On this page you can find all versions of the php package routewise/laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package laravel

Routewise for Laravel

Turn a Laravel app into a safe MCP server for AI clients (claude.ai, Claude Code, any MCP host), on top of laravel/mcp. No OpenAPI spec needed: the app's own code is the source of truth.

Install

Define tools

Register the set (a service provider's boot) and hand the list to your server:

A handler returns anything JSON-encodable. Throw a RuntimeException to tell the model what went wrong.

Routes as tools

From Becomes
HTTP method kind: GET = read, DELETE = delete, the rest = write
Route name invoices.index tool name invoices_index
Path parameters required arguments
The action's FormRequest rules() arguments (type, required, enum, min/max)
#[AgentTool(description: ...)] or the docblock's first line description

Limits: only routes that answer JSON work; nested rules (address.city) are not listed as arguments (they are still validated by the route); rules() that need the live request are skipped.

Turning this on gives the signed-in user's AI client every matching route, with that user's permissions. Start with a narrow include.

OAuth registration

laravel/mcp checks redirect URIs by prefix. Routewise\Http\RestrictOAuthRedirects accepts only the exact callbacks in routewise.exact_redirect_uris, plus http loopback addresses:

Control plane (optional)

php artisan routewise:sync (run on deploy) sends the tool catalog with its scores; calls are sent after each response. Only metadata leaves the app: results are never sent, error messages only with ROUTEWISE_SEND_ERRORS=true, and argument values only for approvals with ROUTEWISE_APPROVAL_VALUES=true.

Rules and approvals

Hard rules live in the app and can't be overridden from anywhere:

With the control plane connected, its dashboard sets a rule per kind and per tool: Allow, Ask first or Block. A call to an "Ask first" tool does not run. The model is told it needs approval, an approver decides on the dashboard, and the same call (same tool, user and arguments) then runs once.

Every call's outcome (ok, failed, blocked, pending, denied) is on the ToolCalled event and in the call log.

Behaviour tests

The readiness scan reads your tool definitions. Behaviour tests ask a model: given this prompt and these tools, which does it call, and with what? No tool is ever run, so they are safe against any database.

Scenarios are PHP files in routewise/ (config behaviour.path) that return Scenario objects:

Testing


All versions of laravel with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
illuminate/console Version ^12.41.1|^13.0
illuminate/http Version ^12.41.1|^13.0
illuminate/routing Version ^12.41.1|^13.0
illuminate/support Version ^12.41.1|^13.0
illuminate/validation Version ^12.41.1|^13.0
laravel/mcp Version ^1.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package routewise/laravel contains the following files

Loading the files please wait ...