MIT
openaaas-mcp-adapter
by Wolido
Related Servers
Alternatives to openaaas-mcp-adapter
Related Servers
OpenLinker Pluginofficial
AlicenseNot gradedqualityAmaintenanceAn MCP bridge that lets Codex and Claude Code interact with OpenLinker agents, and allows the host to serve as a callable agent in the OpenLinker network.Apache 2.0- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.410-
- AlicenseNot gradedqualityDmaintenanceMCP of MCPs. Automatic discovery and configure MCP servers on your local machine. Integration with Claude and Cursor.51Apache 2.0
- AlicenseAqualityCmaintenanceBridges any MCP client (like Claude Code, Zed, VS Code) to any ACP coding agent, enabling multi-agent orchestration from a single chat interface.24175 npm12Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA general-purpose MCP gateway that exposes your local CLI skills to any AI assistant.11 npm1MIT
TDQS
B3.2/5.0
Scored across 15 tools
Disambiguation4/5
Most tools target clearly distinct resources or actions: server config, client registration, service discovery, task lifecycle, and file handling. The main overlap is get_task versus poll_task, since both retrieve task status/results, though their descriptions distinguish one-shot queries from explicit polling.
Naming Consistency4/5
Names are consistently snake_case and mostly follow a verb_noun pattern such as list_services, submit_task, and download_result. Minor deviations are discover and register, which use bare verbs, but the set remains predictable and readable.
Tool Count5/5
The 15 tools are well-scoped for an adapter covering server configuration, client setup, service discovery, task execution, and result file access. Each tool has a plausible role, and the count fits within a reasonable range for the domain.
Completeness4/5
The surface covers the main lifecycle: configure servers, register a client, inspect services, submit and monitor tasks, cancel tasks, and list/download result files. Minor gaps exist, such as no explicit task history/list operation or profile retrieval, but core workflows are covered.
Maintenance
ActivityActive
ResponsivenessWithin a week