
Mcp Data Pipeline Connector
Let your agent query CSV files, Postgres, and REST APIs through one DuckDB-backed MCP connector instead of writing three ad-hoc integrations.
Overview
MCP Data Pipeline Connector is a Build-phase MCP server that connects CSV, Postgres, and REST APIs through DuckDB for agent-driven data work.
What is this MCP server?
- Single MCP surface for CSV, Postgres, and REST API sources
- DuckDB as the query engine for federated reads and transforms
- npm stdio package mcp-data-pipeline-connector
- Reduces one-off scripts when agents need tabular or API-backed data
- YOUR_API_KEY required per published server schema
- Supports 3 source families: CSV, Postgres, REST APIs
- Server version 1.0.0
- Query engine: DuckDB (per description)
What problem does it solve?
Agents and solo devs waste time on separate connectors for spreadsheets, SQL, and REST when one unified query layer would suffice.
Who is it for?
Builders shipping analytics features, internal ops tools, or research agents that must blend files, SQL, and HTTP JSON.
Skip if: Heavy managed ETL-only teams that already standardize on Airbyte or Fivetran without agent involvement.
What do I get? / Deliverables
After registration your agent can reach multiple data sources through one DuckDB-backed MCP toolset for analysis and pipeline steps.
- Unified MCP tools over CSV, Postgres, and REST
- DuckDB-powered query path for agents
- Fewer bespoke data glue scripts in the repo
Recommended MCP Servers
Journey fit
Universal data access is a Build-phase integration task when you are wiring backends, analytics, or agent tools to real datasets. Integrations is the right shelf for a connector that unifies external data sources behind MCP tools for codegen agents.
How it compares
DuckDB federated data MCP connector, not a standalone BI dashboard or markdown data skill.
Common Questions / FAQ
Who is MCP Data Pipeline Connector for?
It is for developers who want their coding agent to read and query CSV, Postgres, and REST data through one MCP server.
When should I use MCP Data Pipeline Connector?
Use it while building integrations or agent tools that need ad-hoc SQL across files and APIs without a full data platform.
How do I add MCP Data Pipeline Connector to my agent?
Install mcp-data-pipeline-connector from npm, configure stdio in your MCP settings, set YOUR_API_KEY, and point DuckDB connection params at your sources.