datasphere-mcp
Related Servers
Alternatives to datasphere-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables read-only interaction with a Databricks workspace, exposing catalog metadata and bounded SQL querying while preserving caller identity through OAuth-protected authorization.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely discover and validate SAP Business Data Cloud contracts (ORD, CSN, share plans) with enterprise guardrails like redaction and read-only defaults.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only interaction with Salesforce orgs through the local sf CLI, providing tools for SOQL queries, object metadata, and field dependencies, while automatically blocking writes to Production orgs.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT, Copilot and Cursor to explore and query SAP S/4HANA's HANA database using SAP's data dictionary, organization structure, CDS views, and read-only SQL, with tools for finding tables, fields, joins, code values, and running SELECT queries. All access is read-only, with encrypted credentials and audited calls.1AGPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to SAP ABAP systems via ADT, retrieving source code, table structures, and other development information through read-only tools.16137 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to inspect databases through read-only tools that explain queries, sample rows, and list indexes, while refusing apply or delete operations.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource and operation: listing spaces, listing objects, reading one object, and inferring dependencies. Overlap between list_objects and get_object is minimal (collection vs single resource), and get_dependencies is clearly separate.
All names follow a consistent snake_case verb_noun pattern (list_spaces, list_objects, get_object, get_dependencies), with no deviations or mixed conventions.
Four tools are well-scoped for a read-only metadata and lineage connector; each covers a core operation without redundancy. The count sits comfortably within the typical 3-15 range.
Core read operations are present, but the surface lacks space-level detail retrieval, search, and any downstream dependency support (explicitly unsupported). The note that output is non-authoritative also signals partial coverage of typical lineage workflows.