A
licenseNot graded
qualityA
maintenanceBridges local MCP hosts to A2A v1-compatible agents, exposing A2A client operations as MCP tools.
10 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.733 PyPI147Apache 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.16125 PyPI24MIT
- AlicenseNot gradedqualityDmaintenanceControl AI agents creation and modification via MCP.881 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with the Phiacta knowledge platform.5 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
B3.2/5.0
Scored across 24 tools
Disambiguation3/5
The viewer tools overlap heavily: viewer_isolate vs viewer_isolate_models, viewer_select vs viewer_highlight_clash, and viewer_get_properties vs viewer_list_clashes all operate on similar element-visibility/data concepts. The descriptions explicitly cross-reference each other ('use X instead'), which mostly resolves selection, but an agent must read carefully to pick correctly.
Naming Consistency4/5
All tools use snake_case verb_noun form, which is readable and consistent. There are minor grouping deviations (some tools carry a viewer_ prefix, some a pynet_ prefix, others are bare like send_command or check_plugin_status), but no camelCase/snake_case mixing.
Tool Count3/5
24 tools is on the heavy side for the apparent scope. The UI/module management and IPC scripting areas are reasonably tight, but the viewer control surface alone accounts for eleven tools and could be consolidated.
Completeness4/5
CRUD for modules and script buttons is largely covered (create/read/update/delete), and the viewer has load, fit, clear, isolate, highlight, select, state, properties, and clash lookup. Minor gaps like no module update/rename and no viewer unload/close keep it from fully complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues