A
licenseA
qualityF
maintenanceA bridge server that enables MCP-compatible AI assistants like Claude to seamlessly discover, communicate with, and manage A2A protocol agents.
7
65 PyPI
146
Apache 2.0
PyNet Bridge
by RAEN-DT
Related Servers
Alternatives to PyNet Bridge
No user-submitted related servers found.
Related Servers
- 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.1692 PyPI24MIT
- AlicenseNot gradedqualityDmaintenanceControl AI agents creation and modification via MCP.1,265 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with the Phiacta knowledge platform.5 npmGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.MIT
- AlicenseCqualityCmaintenanceBridges Aionis execution memory to MCP clients, enabling governed memory context for AI agents.1215 npmApache 2.0
TDQS
B3.4/5.0
Scored across 24 tools
Disambiguation4/5
Most tools have clearly distinct purposes, especially the viewer_* family where select, isolate, highlight_clash, and isolate_models are separated by context. Minor overlap exists between get_buttons_data and get_pynet_ui_layout, and among the several status-checking tools, but descriptions generally resolve the ambiguity.
Naming Consistency4/5
Names are overwhelmingly snake_case and follow verb_noun or viewer_action patterns, making the set easy to scan. There are small inconsistencies such as deploy_script_button instead of create_script_button and inconsistent resource prefixes outside the viewer_* group.
Tool Count4/5
With 24 tools the server is on the heavy side, but the surface spans several real subdomains: viewer control, script-button management, module management, engine command execution, and diagnostics. Each tool appears to earn its place rather than being redundant.
Completeness4/5
Core workflows are well covered: viewer package loading and inspection, clash/property lookup, selection and isolation, script-button CRUD, module creation/deletion, command execution, and status checks. Minor gaps exist, such as no explicit module update/rename or viewer package unload/close operation, but these are workable around.
Maintenance
ActivityMaintained
ResponsivenessNo issues