siGit CLI
mcpothersi.sigit/cli · v1.1.0
Run sigit.si locally: browse repos, search code, manage PRs, issues, and Cloud Sessions.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
# once, as root: cargo install --locked sigit-si-cli --version 1.1.0 --root /usr/local #!/usr/bin/env bash # cli (si.sigit/cli), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-cli.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec uvx mcp-proxy --host 127.0.0.1 --port 8101 --pass-environment -- sigit-si-cli [Unit] Description=MCP server cli (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/cli WorkingDirectory=/var/lib/mcp/cli ExecStart=/opt/mcp/my-agent/bin/cli.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/cli [Install] WantedBy=multi-user.target
connect to it
copy what your client needssigit-si-cli # env: SIGIT_TOKEN, SIGIT_TOOLSETS
{
"mcpServers": {
"cli": {
"command": "sigit-si-cli",
"args": [],
"env": {
"SIGIT_TOKEN": "${SIGIT_TOKEN}",
"SIGIT_TOOLSETS": "${SIGIT_TOOLSETS}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add cli -e "SIGIT_TOKEN=${SIGIT_TOKEN}" -e "SIGIT_TOOLSETS=${SIGIT_TOOLSETS}" -- sigit-si-cli
{
"mcpServers": {
"cli": {
"command": "sigit-si-cli",
"args": [],
"env": {
"SIGIT_TOKEN": "${SIGIT_TOKEN}",
"SIGIT_TOOLSETS": "${SIGIT_TOOLSETS}"
}
}
}
}
{
"servers": {
"cli": {
"type": "stdio",
"command": "sigit-si-cli",
"args": [],
"env": {
"SIGIT_TOKEN": "${SIGIT_TOKEN}",
"SIGIT_TOOLSETS": "${SIGIT_TOOLSETS}"
}
}
}
}
name: my-agent target: local servers: - hub: si.sigit/cli
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.