Sling Cli

io.github.flarcoPublished by GitHub account flarcov1.4.24Updated Oct 24, 2026

Sling CLI MCP server for data pipeline and replication management

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

A local MCP server that exposes Sling CLI so an assistant can manage data pipelines and replication tasks.

What you can do
Manage data pipelines and replication through Sling CLI, driven from the assistant on the local machine. The manifest lists no individual tools, so the exact operations are not documented here. It runs as a local process over stdio and is intended for desktop use only.
When to use it
Consider it when you already use Sling CLI for data replication and want an assistant to help drive pipeline and replication management from your desktop.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, with no web execution. No packages, authentication, environment variables or headers are declared, so the Sling CLI itself presumably must be installed and configured separately.
Before you install
Pipeline and replication management can write, move or overwrite data in source and target systems, so review any operation before it runs. No credentials are declared, but Sling connections may hold database credentials configured outside this server.

Installation

In SourceWeft

  1. Open Sling Cli in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.4.24LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.