F
licenseA
qualityD
maintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.
5
28
-
lava-mcp
by mattface
Related Servers
Alternatives to lava-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that lets agents launch, drive, and read game instances over HTTP, with a dynamic toolset discovered from the running game.71MIT
- AlicenseAqualityFmaintenanceAn MCP server that acts as a proxy to connect MCP clients to agent frameworks like Mastra and LangGraph, enabling agent discovery, dynamic server connections, and recursive agent networks.541 npm10MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- AlicenseAqualityCmaintenanceAn MCP server that connects AI agents to TestOps, enabling test case management, launches, defects, and analytics through natural language.4863 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes Language Server Protocol features to external clients, allowing access to hover information, definitions, completions, references, and rename functionalities.7 npm42MIT
TDQS
B3.4/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct resource or action: device queries (get_device, get_device_dictionary, get_qdl_info) are clearly separated from job operations (submit, cancel, resubmit, set_priority, validate) and listings (list_devices, list_jobs, etc.). No two tools appear to overlap in purpose.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_device, submit_job, list_devices). There are no deviations or mixed conventions.
Tool Count3/5
With 21 tools, the count falls in the 'borderline heavy' range (16-25). While each tool appears necessary, the set could potentially be trimmed by combining some closely related functions, but overall it remains functional.
Completeness4/5
The tool set covers core LAVA workflows: device inspection, job lifecycle (submit, validate, resubmit, cancel, priority), queue/worker status, and lab health. Minor gaps exist (e.g., no device CRUD, no test definition management), but the essential user-facing operations are present.
Maintenance
ActivityInactive
ResponsivenessNo issues