Sling Cli
Let your coding agent configure and run Sling data replication jobs between databases and warehouses without leaving the IDE.
Overview
io.github.flarco/sling-cli is a MCP server for the Build phase that lets agents drive Sling CLI data pipeline and replication management from an IDE.
What is this MCP server?
- MCP wrapper around Sling CLI for pipeline and replication management
- Targets solo builders automating database-to-warehouse or cross-DB sync
- Catalog schema version 1.4.24 on the official MCP server schema
- Stdio-oriented CLI integration pattern (not a hosted remote in listed metadata)
- Focused scope: data movement ops rather than general SQL querying
- Server schema version 1.4.24
- Described as Sling CLI MCP for pipeline and replication management
What problem does it solve?
You know Sling can replicate data but switching between terminal, docs, and agent context breaks flow when wiring pipelines.
Who is it for?
Indie builders using Sling for ETL who want agents to script and adjust replication without constant CLI context switching.
Skip if: Teams that need a hosted warehouse UI only, or builders with no Sling install who want ad-hoc SQL across arbitrary databases.
What do I get? / Deliverables
After registering the server, your agent can orchestrate Sling replication tasks in conversation while you stay in the repo.
- Agent-driven Sling replication and pipeline configuration changes
- Documented sync jobs you can repeat in dev and production
- Faster iteration on data movement without manual CLI-only workflows
Recommended MCP Servers
Journey fit
How it compares
Sling CLI MCP integration, not a managed cloud ETL console or a generic read-only SQL skill.
Common Questions / FAQ
Who is io.github.flarco/sling-cli for?
Solo and small-team developers who already use or plan to use Sling for replication and want Claude Code, Cursor, or similar agents to manage those jobs.
When should I use io.github.flarco/sling-cli?
Use it during build when you are connecting sources to destinations, standing up sync pipelines, or iterating replication config alongside application code.
How do I add io.github.flarco/sling-cli to my agent?
Install and register the MCP server from the Flarco Sling CLI package in your agent’s MCP config, ensure Sling CLI is on PATH, then restart the agent and verify a simple replication or status command.