Sl Mcp

io.github.donovan-jasperPublished by GitHub account donovan-jasperv0.1.2Updated Oct 24, 2026

MCP server for Sapling (sl) version control

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an assistant work with Sapling (sl) version control on the user's machine.

What you can do
  • Run Sapling version control commands through the assistant.
  • Inspect and manage repository state with the sl command-line tool.
  • Point the server at a specific Sapling binary and cap how long commands may run.
  • No individual tools are listed, so the exact command surface is not documented in the supplied material.
When to use it
Useful when you work in Sapling-managed repositories and want an assistant to run version control operations locally instead of switching to a terminal.
Requirements
Runs as a local stdio process installed from the npm package sl-mcp, so Node.js is needed. Sapling must be installed; the SL_MCP_BINARY environment variable can give the path to the Sapling binary. SL_MCP_TIMEOUT optionally sets a command timeout in milliseconds. Desktop only.
Before you install
Version control commands can change repository state, including commits, checkouts and history operations, so review what the assistant runs. The server executes a local binary whose path is configurable via SL_MCP_BINARY; make sure it points to a trusted Sapling installation.

Installation

In SourceWeft

  1. Open Sl Mcp 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.2LatestSep 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.