date: 2026-07-05 title: First stable release

#headline: siGit reaches 1.0 — Git hosting, model repositories, and an MCP server that lets your agent work the repo from the terminal.

siGit is now at version 1.0. Git hosting and open-weights model repositories have run in production for a while; this release marks the point where the platform's API and the tools built on it are stable enough to depend on.

#Model Context Protocol server

The headline of this release is the built-in MCP server at /api/v1/mcp. Point an MCP client (siGit Code, Claude Code, or any conforming client) at it with a bearer token and the agent can work your repositories without leaving the terminal:

• Browse and read: list_repositories, get_file_contents, and search_code let the agent find a repo and read across it.
• Issues and pull requests: list_issues, get_issue, create_issue, list_pull_requests, get_pull_request (with the full three-dot diff), and create_pull_request bring the review workflow into the agent's reach.
• Comments: add_issue_comment posts to an issue or a pull request, which share one per-repository number space.
• Web search: web_search gives the agent a way to find pages, not just fetch known URLs. Search runs through the platform as a signed-in feature rather than a key pasted into every client.

Every tool authorizes against the same repository visibility rules as the rest of the site, so an agent can never reach a private repository its user cannot.

#Accounts and access

• Brokered Google sign-in on the web and the code.sigit.si SPA.
• An admin console for operating the platform.
• OAuth connection status surfaced on the settings page.

#Under the hood

• Repository diffs are read through a hardened git layer that rejects any ref starting with a dash, closing off git argument injection.
• The MCP server is a stateless Streamable-HTTP JSON-RPC endpoint, so it scales with the rest of the app and needs no separate service.