Sling Cli

io.slingdataPublished by slingdata.iov1.4.25Updated Oct 25, 2026

Sling CLI MCP server for querying any database, running data pipelines and managing replications

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

A local MCP server built on the Sling CLI that lets an assistant query databases, run data pipelines and manage replications.

What you can do
Query databases through the Sling CLI from an assistant session. Run data pipelines and move data between sources and targets. Manage and inspect replications. Tool names and parameters are not listed in the supplied material, so exact operations must be checked in the package itself.
When to use it
Useful when you already work with Sling for database queries, pipeline runs or replication management and want an assistant to drive those tasks from the same machine.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package sling over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared, but database connections and credentials are presumably configured through Sling itself.
Before you install
It can run pipelines and manage replications, which may write, move or overwrite data in connected databases, so review actions before approving them. Database credentials are not declared as MCP inputs but will be needed by the underlying Sling configuration; keep them out of shared logs.

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.25LatestSep 16, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • 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.