No user-submitted related servers found.
Scored across 50 tools
Most tools are clearly separated by resource and action, but the three search_pipeline variants (plain, with_filters, with_params) heavily overlap, and list_pipeline_traces, list_pipeline_search_history, and list_search_history all expose query-run data that could be confused. A few other pairs like get_custom_components vs list_custom_component_installations also require careful reading to distinguish.
The vast majority of tools follow a predictable verb_noun pattern (list_workspaces, create_pipeline, get_index, deploy_pipeline), making navigation easy. The object store utilities break the pattern with yq_object_store, sed_object_store, and grep_object_store using Unix-command-style names, and get_from_object_store/get_slice_from_object_store are slightly awkward prepositional forms, but these are a small minority.
At 50 tools, this server is well above the 25+ threshold that indicates an overly large surface. Many tools could be consolidated, such as the three search_pipeline variants and the multiple trace/history retrieval tools, making the set feel more like a raw API dump than a curated MCP tool set.
The server covers the core lifecycle for pipelines, indexes, and workspaces with create, get, list, update, validate, and deploy operations, plus solid tracing, logging, and search history support. However, there are no delete operations for any resource, no way to create or update secrets, and no tool to install or delete custom components, leaving notable dead ends in the workflow.