watsonx.data MCP Proxy
Related Servers
Alternatives to watsonx.data MCP Proxy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides secure integration between MCP clients and IBM Data Intelligence services, enabling AI assistants to interact with IBM's data intelligence capabilities for data management and analytics operations.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA transparent proxy server that simplifies authentication by chaining its own OAuth layer with an upstream MCP server's credentials. It manages dual token sets behind a single interface, enabling secure and streamlined access to protected MCP resources.MIT
- AlicenseNot gradedqualityAmaintenanceA client-side MCP proxy that injects OAuth 2.0 bearer tokens or API keys into MCP requests, enabling MCP clients to connect to OAuth/API-key-protected MCP servers like Amazon Bedrock AgentCore Gateway. It automatically fetches and refreshes credentials using AgentCore Identity or static values.MIT No Attribution
- -licenseNot gradedqualityCmaintenanceMCP server for SAP Datasphere that enables AI assistants to perform data discovery, metadata exploration, analytics queries, ETL data extraction, database user management, and data profiling with built-in PII masking.-

Data Intelligence MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides a modular MCP server to integrate with IBM Data Intelligence services, enabling secure interaction with data intelligence capabilities via tools and skills.19Apache 2.0- AlicenseAqualityAmaintenanceA proxy server that connects MCP clients to the Zihin.ai platform via HTTP, enabling management of AI agents, LLM models, and configuration templates. It provides tools for agent creation and resources for discovering tenant-specific agents and schema templates.96408 npmMIT
TDQS
Scored across 6 tools
The six tools form clear LIST/QUERY pairs for three distinct resource levels: document libraries, document sets, and Presto data assets. Each tool's target and action are unambiguous, and the hierarchical relationship between library and set is explicit.
All tool names follow a consistent uppercase snake_case VERB_NOUN pattern (LIST_* or QUERY_* followed by the resource). There is no mixing of conventions.
Six tools is well-scoped for a query proxy: three resource types each get exactly a list and query operation. No tool feels redundant or missing for the basic query surface.
The surface covers discovery and natural-language querying for document libraries, document sets, and Presto tables. However, it lacks any create/update/delete or ingestion operations, and there is no direct way to list individual documents within a set, so management workflows would hit gaps.