Skip to main content
Glama
shamimlaravel

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to laravel13-livewire4.2.1-mcp

No user-submitted related servers found.

    Related Servers

    • phpustik MCP Server

      halitartuc
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      41
      MIT

    • super-agent-skill

      Akash1070
      A
      license
      C
      quality
      B
      maintenance
      Equips AI coding agents with 62 production-grade tools across 28 modules for persistent memory, live GitHub scouting, UI/UX design, DevOps, security, performance auditing, and SEO/AEO/GEO optimization, enabling automated, development workflows.
      63
      1
      MIT

    • Code-MCP

      millsydotdev
      F
      license
      B
      quality
      Not graded
      maintenance
      Turns AI assistants into full-stack software engineers with 36 tools for cognitive reasoning, code validation, project scaffolding, and AI/IDE configuration generation across 130+ programming languages, databases, and frameworks.
      35
      59 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 75 tools

    Disambiguation2/5

    Several tool pairs are near-duplicates: generate_policy vs generate_full_policy, generate_middleware vs generate_custom_middleware, and fix_bugs vs scan_project_bugs vs deep_scan_bugs. The many convert_*_to_livewire variants and overlapping generator tools also create unclear boundaries. An agent would frequently need to read full descriptions to avoid selecting the wrong tool.

    Naming Consistency3/5

    The toolset broadly follows predictable verb_noun patterns like generate_*, git_*, gh_*, and convert_*_to_livewire. However, there are notable exceptions such as security_audit, fix_bugs, mark_bug_fixed, memorize vs memorize_endpoint vs recall_context, and generate_middleware vs generate_custom_middleware. Overall the style is readable but not consistently disciplined.

    Tool Count1/5

    75 tools is extreme for an MCP server surface, even for a broad Laravel/Livewire toolkit. Many tools could be consolidated, particularly the duplicate policy/middleware/bug-scanning generators. This large count creates significant discovery, selection, and maintenance overhead.

    Completeness4/5

    The toolset covers an impressively wide range: project scaffolding, Livewire components, models, policies, tests, security audits, bug fixes, git/GitHub workflows, versioning, and API/notification generation. It lacks some conventional Laravel generators like migrations, factories, and seeders, but this is a minor gap given the Livewire-centric scope. Typical workflows have no major dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources