Skip to main content
Glama
berry-13

verse-diagnostics-mcp

by berry-13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to verse-diagnostics-mcp

No user-submitted related servers found.

    Related Servers

    • unreal-editor-mcp

      tumourlove
      A
      license
      A
      quality
      F
      maintenance
      Provides build diagnostics and editor log tools for Unreal Engine AI development, enabling Live Coding builds, parsing compile errors, searching/filtering logs, and crash context.
      11
      MIT

    • TracePulse

      sourjya
      A
      license
      Not graded
      quality
      A
      maintenance
      Runtime feedback MCP server for AI coding agents. It watches dev server logs, parses errors, and exposes them as MCP tools so AI agents can instantly verify code changes.
      13 npm
      3
      AGPL 3.0

    • Xcode Errors MCP Server

      nazufel
      F
      license
      Not graded
      quality
      C
      maintenance
      Bridges Xcode and Cursor to provide real-time access to build errors, warnings, and debug output from Xcode's DerivedData, enabling automated error analysis and fixes directly within Cursor.
      -

    • uefn-mcp-pro

      novikit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to work inside a live Unreal Editor for Fortnite session: write and compile Verse, place and wire Creative devices, edit Scene Graph entities, manipulate actors and assets, take screenshots, run playtests, and read editor logs via MCP.
      MIT

    • PythonMCP-UEFN

      yAstrosss
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes the Unreal Editor for Fortnite to AI assistants via MCP, enabling actor manipulation, device property editing, Verse building, and more through a Python bridge.
      3
      GPL 3.0
    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 3 tools

    Disambiguation5/5

    Each tool has a unique purpose: checking log freshness, retrieving raw build output, and getting structured diagnostics. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: check_verse_log_freshness, get_latest_build_session, get_verse_diagnostics.

    Tool Count4/5

    3 tools is appropriate for a focused diagnostics server, though slightly minimal. Each tool serves a clear need without redundancy.

    Completeness5/5

    The tool set covers the full workflow: checking log freshness, retrieving raw build lines, and parsing structured diagnostics. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources