Sl Mcp
Let your agent run Sapling (sl) version-control workflows from chat instead of context-switching to the terminal.
Overview
sl-mcp is a MCP server for the Build phase that connects coding agents to Sapling (sl) version control via configurable CLI execution.
What is this MCP server?
- MCP wrapper around Sapling (sl) for agent-driven version control
- Configurable Sapling binary path via SL_MCP_BINARY
- Command timeout control via SL_MCP_TIMEOUT (milliseconds)
- npm package sl-mcp v0.1.2 with stdio transport
- Published server version 0.1.2 on npm identifier sl-mcp
- Two documented environment variables: SL_MCP_BINARY and SL_MCP_TIMEOUT
What problem does it solve?
Agent-assisted coding breaks flow when every commit, status check, or stack operation requires manual sl commands in a separate terminal.
Who is it for?
Developers already using Sapling who want Claude Code or Cursor to drive sl workflows with explicit binary and timeout controls.
Skip if: Teams on pure Git/GitHub without Sapling installed, or anyone needing hosted PR review MCP instead of local sl.
What do I get? / Deliverables
Your agent can invoke Sapling operations through MCP so repo state stays in sync with generated patches and reviews.
- Agent-executed Sapling commands with timeout-bounded responses
- Repository status and stack operations surfaced inside the agent thread
Recommended MCP Servers
Journey fit
How it compares
Sapling CLI integration MCP, not a GitHub Issues or GitLab merge-request server.
Common Questions / FAQ
Who is sl-mcp for?
Solo builders and small teams on Sapling who want their coding agent to run sl commands safely through Model Context Protocol.
When should I use sl-mcp?
Use it during active Build work when agents create patches and you need automated status, commit, or stack operations without leaving the agent session.
How do I add sl-mcp to my agent?
Install npm package sl-mcp, configure stdio in your MCP client, set SL_MCP_BINARY to your sl path if needed, and optionally SL_MCP_TIMEOUT for long commands.