si.sigit/sigit is an MCP server that MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search. Its tool list has not been published yet, requires no API key, and scores 55/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"si-sigit-sigit-getsigit": {
"args": [
"-y",
"@smbcloud/sigit"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
siGit Code is a local coding agent. It runs on your machine, not someone else's. No API keys, no cloud round-trips, no subscription.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@smbcloud/sigit' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @smbcloud/sigit against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in search
An autonomous agent that conducts deep research on any data using any LLM providers
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
The official MCP server implementation for the Perplexity API Platform
Production ready MCP server with real-time search, extract, map & crawl.
MCP Security Weekly
Get CVE alerts and security updates for si.sigit/sigit and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
siGit Code is a local coding agent. It runs on your machine, not someone else's. No API keys, no cloud round-trips, no subscription.
Its home is code.sigit.si. You can run it yourself, as below, or use the hosted version (siGit Code Cloud) there if you would rather not run a model locally. sigit.si is Git hosting built for AI workflows.
It works in any codebase. In smbCloud repos it is more useful out of the box because it already understands the Rust workspace layout, deploy flows, auth boundaries, and GresIQ.
You can use it in two ways:
sigit for the interactive chat UI| Platform | ACP mode | Terminal mode |
|---|---|---|
| macOS | ✓ | ✓ |
| Linux | ✓ | ✓ |
| Windows | ✓ | not yet |
cargo install sigit
| Method | Command |
|---|---|
| Homebrew | brew tap getsigit/tap && brew trust --tap getsigit/tap && brew install sigit |
| pip | pip install sigit-code |
| uv | uvx --from sigit-code sigit |
| npm | npm install -g @smbcloud/sigit |
The first launch downloads a GGUF model from Hugging Face. Expect roughly 1 to 2 GB, depending on the model. After that, loads come from disk and are much faster.
On macOS, siGit Code shares its model cache with the desktop app through an App Group container. If the desktop app already downloaded the model, the CLI reuses it.
Add this to ~/.config/zed/settings.json:
{
"agent_servers": {
"siGit Code": {
"type": "custom",
"command": "/absolute/path/to/sigit"
}
}
}
Use the full absolute path. ~ does not expand here.
In Xcode, open Settings > Intelligence > Agents, add a custom agent, and set:
sigit--acpThe explicit --acp mode is designed for Xcode: it loads the selected on-device
model on the first prompt, so you do not need to send /load from the Xcode chat.
To let siGit use Xcode's build, test, and project tools, enable Allow external
agents to use Xcode tools in Xcode's Intelligence settings, keep the project
open, and add this to ~/.config/sigit/mcp.toml:
[[server]]
name = "xcode"
command = "xcrun"
args = ["mcpbridge"]
Install from the Visual Studio Code Marketplace.
{
"sigit.agents": {
"sigit": {
"name": "siGit (on-device)",
"command": "sigit",
"args": [],
"env": {}
},
},
"sigit.agent.default": "sigit"
}
Install ACP Client, then add:
{
"acp.agents": {
"siGit Code": {
"command": "sigit",
"args": [],
"env": {}
}
}
}
Run sigit in a terminal and you get the same model and system prompt as the editor integ