| 1 | --- |
| 2 | date: 2026-07-05 |
| 3 | title: First stable release |
| 4 | headline: siGit reaches 1.0 — Git hosting, model repositories, and an MCP server that lets your agent work the repo from the terminal. |
| 5 | --- |
| 6 | |
| 7 | siGit is now at version 1.0. Git hosting and open-weights model repositories |
| 8 | have run in production for a while; this release marks the point where the |
| 9 | platform's API and the tools built on it are stable enough to depend on. |
| 10 | |
| 11 | ## Model Context Protocol server |
| 12 | |
| 13 | The headline of this release is the built-in MCP server at `/api/v1/mcp`. Point |
| 14 | an MCP client (siGit Code, Claude Code, or any conforming client) at it with a |
| 15 | bearer token and the agent can work your repositories without leaving the |
| 16 | terminal: |
| 17 | |
| 18 | - **Browse and read**: `list_repositories`, `get_file_contents`, and |
| 19 | `search_code` let the agent find a repo and read across it. |
| 20 | - **Issues and pull requests**: `list_issues`, `get_issue`, `create_issue`, |
| 21 | `list_pull_requests`, `get_pull_request` (with the full three-dot diff), and |
| 22 | `create_pull_request` bring the review workflow into the agent's reach. |
| 23 | - **Comments**: `add_issue_comment` posts to an issue or a pull request, which |
| 24 | share one per-repository number space. |
| 25 | - **Web search**: `web_search` gives the agent a way to find pages, not just |
| 26 | fetch known URLs. Search runs through the platform as a signed-in feature |
| 27 | rather than a key pasted into every client. |
| 28 | |
| 29 | Every tool authorizes against the same repository visibility rules as the rest |
| 30 | of the site, so an agent can never reach a private repository its user cannot. |
| 31 | |
| 32 | ## Accounts and access |
| 33 | |
| 34 | - Brokered Google sign-in on the web and the code.sigit.si SPA. |
| 35 | - An admin console for operating the platform. |
| 36 | - OAuth connection status surfaced on the settings page. |
| 37 | |
| 38 | ## Under the hood |
| 39 | |
| 40 | - Repository diffs are read through a hardened git layer that rejects any ref |
| 41 | starting with a dash, closing off git argument injection. |
| 42 | - The MCP server is a stateless Streamable-HTTP JSON-RPC endpoint, so it scales |
| 43 | with the rest of the app and needs no separate service. |