Sling Cli
io.github.flarco/sling-cli is a MCP server that lets agents drive Sling CLI data pipeline and replication management from an IDE.
About
io.github.flarco/sling-cli exposes the Sling command-line workflow to MCP-compatible agents such as Claude Code and Cursor. developers shipping analytics features, internal dashboards, or migration tooling can ask an agent to reason about replication jobs, connections, and pipeline tasks instead of memorizing every Sling subcommand. The server description centers on data pipeline and replication management, which maps cleanly to backend and data-layer integration work. You should reach for this when your product needs repeatable sync between operational stores and analytical systems and you already standardize on Sling in scripts or CI. It is narrower than a full orchestrator UI or a generic database MCP: it assumes Sling is your replication engine. Pair it with schema migration skills and monitoring MCPs once pipelines run in production.
- 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
Sling Cli by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
What it does
Let your coding agent configure and run Sling data replication jobs between databases and warehouses without leaving the IDE.
Who is it for?
Best when you use Sling for ETL and want agents to script and adjust replication without constant CLI context switching.
Skip if: Skip if you need a hosted warehouse UI only, or developers with no Sling install and want ad-hoc SQL across arbitrary databases.
What you get
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
By the numbers
- Server schema version 1.4.24
- Described as Sling CLI MCP for pipeline and replication management
Recommended MCP Servers
1ClickReport40 tools for marketing analytics, campaign management, and AI monitoring across 6 platforms.
222wcnm BilistalkermcpTrack Bilibili creators and get the latest updates on videos, dynamics, and articles.7
ABMeterFeature flagging and A/B testing platform with AI-first experimentation workflows.
Abs McpQuery the ABS in plain English — CPI, labour force, building approvals, migration, GDP.
AdAdvisor MCP ServerQuery Meta Ads performance data — accounts, campaigns, ad sets, ads, metrics & settings.
ADCIRC Model Setup MCP ServerADCIRC model configuration debugging, parameter lookup, and validation5How it compares
Sling CLI MCP integration, not a managed cloud ETL console or a generic read-only SQL skill.
FAQ
Who is io.github.flarco/sling-cli for?
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.