A
licenseNot graded
qualityA
maintenanceBridges local MCP hosts to A2A v1-compatible agents, exposing A2A client operations as MCP tools.
5 npm
MIT
PyNet Bridge
by RAEN-DT
Related Servers
Alternatives to PyNet Bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceA bridge server that enables MCP-compatible AI assistants like Claude to seamlessly discover, communicate with, and manage A2A protocol agents.730 PyPI148Apache 2.0
- AlicenseBqualityFmaintenanceA bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.1696 PyPI24MIT
- AlicenseNot gradedqualityDmaintenanceControl AI agents creation and modification via MCP.335 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with the Phiacta knowledge platform.7 npmGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.MIT
TDQS
A3.5/5.0
Scored across 23 tools
Disambiguation5/5
Each tool has a clear, distinct purpose. Viewer tools (viewer_select, viewer_highlight_clash, viewer_isolate) are differentiated by their specific actions. Module/script tools are well-separated. The only slight overlap is between send_command and send_command_by_path, but their descriptions clarify the difference (inline content vs file path).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case. Viewer tools use a 'viewer_' prefix grouping related functionality. Verbs are imperative and clear (create, delete, get, list, send, etc.). No mixing of camelCase or other conventions.
Tool Count4/5
23 tools is on the higher end but reasonable for the scope of managing a plugin system and a BIM viewer. While borderline, each tool seems necessary for the domain, and there are no redundant tools. The count is slightly above ideal but still manageable.
Completeness3/5
The tool set covers CRUD for modules and script buttons well, but the viewer side has gaps: no tool to unload a package, close the viewer, or list available script commands. Additionally, viewer_isolate is noted as not yet functional, representing a missing feature. Some operations like updating a script button's content are present, but the overall coverage is not fully comprehensive.
Maintenance
ActivitySlowing
ResponsivenessNo issues