Skip to main content
Glama
dbsectrainer

mcp-data-pipeline-connector

by dbsectrainer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-data-pipeline-connector

No user-submitted related servers found.

    Related Servers

    • motherduck-mcp

      ampcome-mcps
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for SQL analytics on DuckDB and MotherDuck databases, enabling AI assistants and IDEs to query data via natural language.
      1
      MIT

    • DuckDB MCP Server

      MMHK
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server enabling AI assistants to query and analyze data via DuckDB SQL engine, supporting local files, memory, S3, and MotherDuck.
      27 npm
      Apache 2.0

    • duckdb-mcp

      wuqunfei
      A
      license
      A
      quality
      A
      maintenance
      A minimal MCP server that provides a persistent DuckDB SQL engine to AI assistants, enabling natural-language querying of CSVs, Parquet, and cloud data with 12 tools and optional read-only mode.
      12
      MIT

    • duckcoop

      minsc-of-secrets
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for sandboxed, read-only SQL queries on CSV/Parquet/JSON files via DuckDB, limited to a specified directory.
      1
      MIT

    • Zaturn

      kdqed
      A
      license
      A
      quality
      C
      maintenance
      An open-source MCP server that connects to various data sources (SQL databases, CSV, Parquet files), allowing AI models to execute SQL queries and generate data visualizations for analytics and business intelligence.
      12
      75
      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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: connection registration, listing sources, tables, schemas, querying, transforming, and health checks. No two tools have overlapping purposes, making selection unambiguous.

    Naming Consistency5/5

    All tool names follow an imperative verb pattern (connect_source, list_sources, list_tables, get_schema, check_health), with 'query' and 'transform' as clear single-verb actions. The convention is consistent and predictable.

    Tool Count5/5

    Seven tools cover the core pipeline connector workflow without bloat. Each tool serves a distinct function and contributes to the overall purpose, making the count well-scoped.

    Completeness4/5

    The surface covers source registration, discovery, schema inspection, querying, transformation, and health monitoring. Minor gaps exist (no delete/update source), but the core lifecycle of connecting and exploring data is well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources