Skip to main content
Glama
Sign In
bladewell

bladewell

by rkwebforge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to bladewell

No user-submitted related servers found.

    Related Servers

    • LocalDev MCP

      mehrdad03
      A
      license
      B
      quality
      D
      maintenance
      A 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.
      49
      1
      MIT
    • Elfsight MCP Server

      Elfsight MCP Serverofficial

      elfsight
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP-capable AI agent to browse and manage a chosen workspace’s apps, projects, and widgets, including creating widgets from templates, updating settings, publishing changes, and retrieving install code.
      MIT

    • mcp-server-laravel

      rendi-febrian
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      9 npm
      MIT

    • 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
    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

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools mostly target distinct operations: browsing the catalog, inspecting one component, checking project install state, and adding/updating components. There is some overlap between list_components and project_status because both can reveal installed status, but the descriptions make the intended distinction reasonably clear.

    Naming Consistency4/5

    Most names follow a clear verb_noun pattern: list_components, get_component, add_components. project_status is a noun phrase rather than a verb-led name, which is a minor deviation but still readable and understandable.

    Tool Count5/5

    Four tools is a well-scoped surface for a focused component-library management server. Each tool covers a distinct part of the workflow: discover, inspect, check status, and install/update.

    Completeness4/5

    The surface covers the core lifecycle: listing available components, inspecting details, checking installation state, and adding or updating components. A remove/uninstall operation is an obvious minor gap, but most agent workflows can be completed with the existing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources