MCP Data Pipeline Connector

Universal data connector for CSV, Postgres, and REST APIs via DuckDB

One MCP server for all your data sources — with cross-source SQL joins and no external query service. DuckDB runs embedded in-process, so you can join a CSV file against a Postgres table against a REST API response in a single query, entirely on your machine. Agents work with your data without needing source-specific knowledge or multiple MCP server configs.

Tool reference|Configuration|Contributing|Troubleshooting

{ "mcpServers": { "data-connector": { "command": "npx", "args": ["-y", "mcp-data-pipeline-connector@latest"] } } }

Define your data sources in~/.mcp/data-sources.yaml:

sources: - name: sales type: csv path: ~/data/sales-2025.csv - name: users type: postgres connection_string: "${POSTGRES_URL}" tables: [users, subscriptions]

Store connection strings in environment variables, not directly in the YAML file.

Amp · Claude Code · Cline · Cursor · VS Code · Windsurf · Zed

Place a CSV file at~/data/sample.csv, add it as a source in your config, then enter:

What columns are in the sample table? Show me the first 5 rows.

Your client should return the schema and a preview of the data.

Path to the YAML file defining data sources.

Type:stringDefault:~/.mcp/data-sources.yaml

Time-to-live in seconds for cached REST API responses. Set to0to disable caching.

Maximum number of rows returned by a singlequerycall. Prevents accidental large result sets.

Reject any SQL statements that are notSELECTqueries. Enforces read-only access across all sources.

Pass flags via theargsproperty in your JSON config:

{ "mcpServers": { "data-connector": { "command": "npx", "args": ["-y", "mcp-data-pipeline-connector@latest", "--max-rows=5000", "--rest-cache-ttl=60"] } } }

Before publishing a new version, verify the server with MCP Inspector to confirm all tools are exposed correctly and the protocol handshake succeeds.

npm run build && npm run inspect

# List all tools npx @modelcontextprotocol/inspector --cli node dist/index.js --method tools/list # List resources and prompts npx @modelcontextprotocol/inspector --cli node dist/index.js --method resources/list npx @modelcontextprotocol/inspector --cli node dist/index.js --method prompts/list # Call a tool (example — replace with a relevant read-only tool for this plugin) npx @modelcontextprotocol/inspector --cli node dist/index.js \ --method tools/call --tool-name list_sources # Call a tool with arguments npx @modelcontextprotocol/inspector --cli node dist/index.js \ --method tools/call --tool-name list_sources --tool-arg key=value

Run before publishing to catch regressions in tool registration and runtime startup.

Each connector lives insrc/connectors/and must implement theDataConnectorinterface. Add fixture data files undertests/fixtures/for integration tests. Never log connection strings or credentials — sanitize before any output or error message.

mcp-data-pipeline-connectoris listed onMCP RegistryandMCP Market.

Maritime intelligence for tracking vessels, analysing ports, and exploring ship data.