openroad-mcp
Related Servers
Alternatives to openroad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) Server for the mcp API.1,026 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes KiCad PCB design automation tools to AI assistants and other MCP clients.-
- AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server that provides JSON-RPC functionality through OpenRPC.238 npm43Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server scaffold for building and deploying custom MCP tools using the mcp-framework.-
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseNot gradedqualityDmaintenanceMCP Server simplifies the implementation of the Model Context Protocol by providing a user-friendly API to create custom tools and manage server workflows efficiently.14 npm4MIT
TDQS
Scored across 10 tools
The query/exec split is clearly disambiguated by read-only vs state-modifying behavior with explicit cross-references. Session management, command execution, and report image tools each have distinct targets, though inspect_interactive_session and get_session_metrics have slight semantic overlap.
Most tools follow a clear verb_noun pattern: list/create/terminate/inspect/get/read. However, interactive_openroad_query and interactive_openroad_exec put the verb at the end and do not match the otherwise consistent session/report naming pattern.
Ten tools is well-scoped for the server's purpose: command execution, session lifecycle, session introspection, and report image access. Each tool has a clear role and no redundant additions inflate the count.
The tool surface covers session creation/listing/termination, read/write command execution, history/metrics, and report image retrieval. Minor gaps exist, such as no explicit session attach or live output streaming, but the core workflows are fully usable without dead ends.