bladewell
Related Servers
Alternatives to bladewell
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA guarded Model Context Protocol server that lets AI assistants inspect, edit, test, and validate explicitly approved local software projects, featuring 49 focused MCP tools for project discovery, safe editing, Git inspection, Laravel integration testing, and more.491MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to introspect a Laravel application's routes, models, controllers, migrations, and more through the Model Context Protocol, running locally via php artisan commands and filesystem scanning.8 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to deeply interact with the PHP ecosystem, including runtime, static analysis, security scanning, testing, Composer, and frameworks like Laravel and Symfony. It exposes over 30 tools, 8 resources, and 7 prompts via MCP, allowing natural language commands to run PHP linting, static analysis, audits, tests, and project initialization.41MIT
- AlicenseBqualityBmaintenanceExposes Laravel development tools (artisan, migrations, config, schema, logs) as MCP tools for use with compatible clients.234 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables secure execution of Laravel Artisan commands through AI assistants, allowing controlled management of Laravel projects via natural language.6MIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude or any MCP client to Laravel Herd, providing 218 tools to manage PHP development environments, Laravel projects, sites, services, database, and more through natural language.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: list_components browses/searches the catalog, get_component gives deep detail on one component, project_status reports the app's install state, and add_components installs/updates files. The list-vs-get split is a well-understood pattern, and status vs install are cleanly separate concerns.
Three of four tools follow a clean verb_noun pattern (list_components, get_component, add_components), all lowercase snake_case. project_status deviates with a noun_noun form without an action verb, a minor inconsistency but still readable and predictable.
Four tools is a tight, focused set that maps cleanly onto the browse-inspect-check-install workflow for a component library. It is slightly lean and a few operations (e.g. removal) are folded into add_components, but each tool earns its place.
The surface covers discovery, detailed inspection, install/update, and environment/status checks, which is most of the lifecycle. The notable gap is that no tool removes or uninstalls components, and update detection is only aggregate via project_status rather than per-component.