No user-submitted related servers found.
Scored across 36 tools
Most tools have clearly distinct purposes. The only potential confusion is between import_source_metadata and import_and_wait, and among list_available_tables, list_kb_tables, and discover_tables, but their descriptions clarify the different stages. Overall, an agent can reliably select the right tool.
Tool names overwhelmingly follow a consistent verb_noun pattern with clear prefixes like list_, get_, create_, update_, delete_. The use of KB/KC abbreviations is consistent within entities. The only outlier is whoami, but it's a standard connectivity check and doesn't break the pattern.
36 tools is excessively high for a coherent MCP surface, exceeding the 25-tool threshold. The server bundles multiple subdomains (sources, destinations, KBs, KCs, pipelines, agents) into one toolset, which would be better split into focused servers.
The toolset covers the core ingestion-to-pipeline workflow well, including source listing, import, KB/KC management, and SQL generation. However, there are notable gaps: no update or delete for sources, no direct KB delete, no destination creation, and no pipeline execution/trigger tool. This creates dead ends for lifecycle management.
