Run sigit.si locally: browse repos, search code, manage PRs, issues, and Cloud Sessions.
{ "mcpServers": { "si.sigit-cli": { "command": "cargo", "args": [ "sigit-si-cli" ], "env": { "SIGIT_TOKEN": "<secret>", "SIGIT_TOOLSETS": "<value>" } } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
cargo sigit-si-cliClaude Code has no install link for a local command. Copy the command below and run it in a terminal.
SIGIT_TOKEN=<secret> SIGIT_TOOLSETS=<value> claude mcp add si.sigit-cli -- cargo sigit-si-cliRun in a terminal.
{ "mcpServers": { "si.sigit-cli": { "command": "cargo", "args": [ "sigit-si-cli" ], "env": { "SIGIT_TOKEN": "<secret>", "SIGIT_TOOLSETS": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: SIGIT_TOKEN, SIGIT_TOOLSETS.
SiGit CLI runs locally over stdio.
Last checked 2026-10-26. Run sigit.si locally: browse repos, search code, manage PRs, issues, and Cloud Sessions.
From the publisher
README is not crawled yet. Open the repository