si.sigit/cli
OfficialResolves repository context from the local Git checkout — it reads the sigit.si Git remote in the current directory to infer the OWNER/NAME so repository-scoped tools default to the repo you're standing in, and defaults a new pull request's head to the checked-out branch.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
sigit-si-cli
si is the command line interface for sigit.si — sign in,
manage repositories, review pull requests, triage issues, search code, and
drive Cloud Sessions, all from the terminal.
Install
cargo install --path crates/cliThis installs a binary named si. On a machine with the .NET SDK there is also
a prebuilt tool:
dotnet tool install --global SiGit.CliRelated MCP server: SwarmMojo MCP Server
Usage
si auth login # sign in with your sigit.si account
si repo list # your repositories
si repo create my-project --private
si repo clone seto/my-project # clone with your sign-in, no token in the URL
si auth setup-git # or let plain `git clone` use it too
# Inside a repo checkout, si infers OWNER/NAME from the sigit.si git remote —
# --repo is only needed when you're not standing in one.
si pr list
si pr view 42
si pr create --title "Fix the thing" --base main
si issue list --state open
si issue create --title "Bug: ..." --body "Steps to reproduce..."
si code search "TODO" --ref main
si code view README.md
si status set HEAD --state success --context ci/test
si status view # the checks on HEAD
si run start --repo seto/app "Fix the failing build"
si run list
si run view 12 # status and the end of the transcript
si site publish --wait # publish the default branch as a site
si site view
si session new --title "Refactor auth"
si models
si billing show
si auth signup # also: resend, reset-password, delete-account
si browse # open the current repo on sigit.si
si api repos # raw escape hatch for any endpointPass --json to any read command for machine-readable output.
As an MCP server
si mcp serves these same commands to an AI agent as
MCP tools over stdio:
{
"mcpServers": {
"sigit": { "command": "si", "args": ["mcp"] }
}
}There is nothing to authenticate — the server reuses the token si auth login
stored. Point your editor at the directory of a checkout and repository tools
default to the repo you're standing in, so the agent can say "list the open
pull requests" without naming one; create_pull_request likewise defaults its
head to the checked-out branch.
Trim the tool list when an agent doesn't need all of it:
si mcp --read-only # drop every tool that writes
si mcp --toolsets repo,issue,pr,code # or SIGIT_TOOLSETS=repo,issueToolsets are account, repo, issue, pr, code, hook, session, and
billing. sigit.si also hosts a remote MCP server at /api/v1/mcp for clients
that would rather connect over HTTP than spawn a binary.
Environments
si --environment dev repo list # a local sigit.si server (localhost:3000)
SIGIT_HOST=staging.example.com si repo listCredentials are stored per-environment in ~/.sigit/token (or
~/.sigit-dev/token). SIGIT_TOKEN overrides the stored token, which is how
CI authenticates without an interactive login.
Workspace layout
crates/sigit-si-api— a standalone, typed Rust client for the sigit.si JSON API. No CLI dependencies (clap, dialoguer, …); usable from any Rust project that wants to talk to sigit.si.crates/cli— thesibinary: command parsing, terminal rendering, git remote resolution, and credential storage, built on top ofsigit-si-api.
Issues, pull requests, and code search have no REST surface on sigit.si yet —
they're served over the same MCP (Model Context Protocol) JSON-RPC endpoint
the AI agent uses. sigit-si-api speaks that transport internally; it's not
visible at the call site.
MCP Registry listings
This repo publishes two entries to the official MCP Registry, one per way of reaching the same tools, so registry-aware clients can add either in one click:
Listing | File | What it is |
|
| This CLI: a cargo package listing that runs |
|
| The hosted server at |
The CLI holds server.json because it's what this repo ships, and that's the
filename mcp-publisher defaults to. Sibling listings are named after their
own leaf, so the file says which entry it publishes.
Both go out through the release-mcp-registry.yml workflow, and both prove
namespace ownership with a DNS TXT record on sigit.si rather than GitHub
OIDC, so one credential covers the pair. A package listing has a second hurdle:
the registry fetches the crate from crates.io and looks for the
mcp-name: si.sigit/cli marker in its README, which is why that marker sits in
this file. Crate versions are immutable, so a release that ships without the
marker can never be listed, and fixing it costs a new version. The internal
setup and release runbook live with the server (private sigit-si repo).
To cut a release, bump [workspace.package].version and the sigit-si-api
dependency in the root Cargo.toml, merge development into main, and push a
vX.Y.Z tag. release-crates.yml checks the crate versions against the tag,
publishes whichever of sigit-si-api and sigit-si-cli isn't on crates.io yet
(through Trusted Publishing, so no token is stored), then dispatches
release-mcp-registry.yml.
Development
make build # cargo build --workspace
make test # cargo test --workspace
make lint # cargo clippy --workspace --all-targets -- -D warnings
make fmt # cargo fmt --all
make check # fmt + lint + testDisclaimer
All em dashes are written by Seto Elkahfi.
License
Apache-2.0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Hosted coding agent: start, follow up on and stop tasks that can open GitHub pull requests.
Git-backed platform for skills, tools, and context for AI agents
Related MCP Servers
- AlicenseAqualityAmaintenanceServes local coding-agent session history over stdio, letting MCP-capable agents search past sessions across Codex, Claude Code, Gemini CLI, OpenCode, jcode, and Pi and read bounded, secret-redacted transcripts. Read-only mode restricts it to search and transcript tools, while write-enabled mode can create copies of a conversation in another agent's native format.463MIT
- AlicenseNot gradedqualityBmaintenanceEnables compatible agents to call registered local tools and read resources through one stdio server, including harness preparation, knowledge search and document management, memory retention/recall, correction proposals, advisory decisions, tool/skill discovery, and log/source inspection.2Apache 2.0
- AlicenseAqualityCmaintenanceExposes the customer-support tool registry over stdio so Claude Desktop or Claude Code can look up customers and orders, track shipments, search help-center articles, update shipping addresses, issue policy-checked refunds and escalate to a human. It reuses the same pydantic validation, ownership and refund policy, approval gate and audit logging as the HTTP agent, with the customer identity taken from server configuration rather than the model.7MIT
- AlicenseNot gradedqualityCmaintenanceExposes policy, control, risk and system lookup tools plus an agent-as-a-tool query endpoint over stdio or streamable HTTP, so clients can run hybrid and graph retrieval, traverse knowledge-graph neighbors, and assess control-coverage gaps. Answers come back cited and guardrailed, and it runs fully offline without API keys.MIT