Related Servers

Several tools have unclear boundaries: mcp_add vs capability_register, mcp_remove vs capability_unregister, mcp_update vs capability_configure, and mcp_add_from_discovery vs capability_register are nearly identical in purpose, with descriptions explicitly noting they share the same catalog/policy path. mcp_list, mcp_query_by_protocol, and various discovery tools have distinct scopes but overall the set is hard to distinguish.

Mixed conventions: snake_case throughout but with inconsistent prefixes (mcp_*, capability_*, discovery_*, partner_*, environment_*, compat_*) and no predictable pattern. The use of both mcp_ and capability_ prefixes for essentially the same operations further breaks consistency.

22 tools is on the high side for a server whose purpose seems to be managing MCP integrations and discovery. While each tool has a hypothetical role, many are redundant (e.g., multiple add/remove/update paths), making the surface feel heavy.

Core lifecycle operations (add, remove, update, list) are present, but the domain—managing MCP adapters, discovery, and blacklisting—has notable gaps: no explicit tool for querying tool details (except mcp_explain_tool), no pagination for mcp_list, and no clear way to manage partner connections beyond listing. Some operations are only partially covered.