Skip to main content
Glama
stkim3

datasphere-mcp

by stkim3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to datasphere-mcp

No user-submitted related servers found.

    Related Servers

    • Databricks MCP

      Agent-Hellboy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only interaction with a Databricks workspace, exposing catalog metadata and bounded SQL querying while preserving caller identity through OAuth-protected authorization.
      MIT

    • sap-bdc-mcp

      rahulsethi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      4
      MIT

    • Salesforce MCP Server

      NeverEndingCode
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1
      MIT

    • SAP HANA MCP Server

      HelpCode-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      AGPL 3.0

    • SAP WebGUI MCP

      arc-mcp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to perform administrator-approved, read-only SAP WebGUI lookups of DDIC table fields, data elements, domains, and displayed source over BTP principal propagation. Live reads are disabled by default and require each exact object to be approved and each verified principal mapped to an expected SAP user.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (list_spaces, list_objects, get_object, get_dependencies), with no deviations or mixed conventions.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources