Watsonx.data Document Libraryofficial
A
licenseNot graded
qualityC
maintenanceBridges AI agents with watsonx.data document libraries, enabling natural language queries and intelligent retrieval from document libraries.
4
Apache 2.0
IBM watsonx.data MCP Server
Officialby IBM
Related Servers
Alternatives to IBM watsonx.data MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Databricks workspaces through natural language, supporting SQL queries, cluster management, jobs, Genie AI, Unity Catalog, and more.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and explore distributed data across EdgeLake nodes through SQL operations, resource discovery, and schema inspection. Supports complex queries with joins, aggregations, and metadata fields across multiple databases and tables.Mozilla Public 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to audit data governance, check access control roles, query namespaces, and inspect Iceberg metadata.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to execute SQL queries and explore databases, tables, and catalogs on Databricks using Unity Catalog.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with SQL Server databases through natural language, providing capabilities for executing queries, exploring schemas, analyzing performance, backing up tables, and managing data with built-in safety limits.-
TDQS
B3.4/5.0
Scored across 39 tools
Disambiguation5/5
Each tool targets a distinct action and resource. Even though there are many engine-specific tools (e.g., create_presto_engine vs create_prestissimo_engine), the tool names and descriptions clearly differentiate them. Overlapping concepts like pause/resume are separated by engine type, making selection unambiguous.
Naming Consistency4/5
Most tools follow a verb_noun pattern (create_schema, list_engines, execute_select). There is slight inconsistency: 'get' vs 'list' for retrieval tools (e.g., get_instance_details vs list_engines), and 'describe_table' uses 'describe' instead of a more uniform prefix. Overall, the convention is predictable.
Tool Count3/5
With 39 tools, the set is on the higher side. Many tools are redundant because they duplicate the same operations for different engine types (Presto, Prestissimo, Spark). While each tool serves a purpose, the count feels heavy for a typical MCP server, bordering on excessive.
Completeness2/5
Several lifecycle operations are missing: no tool to delete engines, schemas, or tables, and no create_table tool exists. Additionally, there is no way to list catalogs, which are referenced in many operations. These gaps would cause agent failures when trying to perform basic data management tasks.
Maintenance
ActivityMaintained
ResponsivenessNo issues