Skip to Content
Gitza is open. Create your account and push your first repository in South Africa.
AI tools and MCP

AI tools and MCP

Gitza MCP lets compatible AI clients read repository files, branches, commits, issues and pull requests. You can also allow them to create issues, add comments and open pull requests from branches you have already pushed to the selected repository. Fork-qualified source branches are not supported.

The MIT-licensed source lives in the standalone Gitza MCP repository . Version 0.1.0 is available as @gitza/mcp on npm , from the Gitza release page , and at https://mcp.gitza.co.za/mcp. Operators can also build the package and deploy their own service using its operations guide .

Connect locally

The local package requires Node 24 or newer. Install the pinned release:

npm install -g @gitza/mcp@0.1.0

Create a token under Settings → Applications in Gitza, restricted to the repositories you want to use. For reading, select read:repository and read:issue. For writing, select write:repository and write:issue.

Make GITZA_TOKEN available securely in your client’s launch environment. Do not put it in a shared configuration file, Git repository or command history. Then register the installed executable in Claude Code:

claude mcp add --transport stdio --scope user gitza --env GITZA_REPOSITORIES=you/project -- gitza-mcp stdio

The client must inherit the token environment variable. If it does not, use the client’s secure secret configuration. GITZA_REPOSITORIES is a comma-separated allowlist. Access is read-only unless you also set GITZA_WRITE=true.

Open /mcp in Claude Code to check the connection. Start with a read such as “List the files in you/project”. Other clients can use the JSON configuration in the MCP README .

Connect to the hosted service

Use the Gitza endpoint without installing the local package:

claude mcp add --transport http --scope user gitza https://mcp.gitza.co.za/mcp

Run claude mcp login gitza, or open /mcp in Claude Code. Follow browser sign-in, choose your repositories and decide whether to enable the three write actions. No repository is selected by default. Repositories added later are not automatically included.

Visit your connections  to revoke a connection immediately, or to remove every connection and the stored account credential. You can also revoke the authorised application in your Gitza account settings.

Access and privacy

Every request checks your current Gitza access as well as your connection’s permissions. Removing organisation access takes effect on subsequent requests. A renamed or replaced repository must be selected again.

Hosted connections store an encrypted Gitza account credential. That credential can be broader than your selected repositories; the MCP service applies the repository and action limits you approved. Local connections use your token directly and do not send it to a separate broker.

Content returned to your AI client may be processed by its model provider outside South Africa. Hosting MCP locally or in South Africa does not determine where your AI provider processes responses. Review your provider’s settings and your organisation’s policies before connecting private repositories.

What to expect

Files and diffs are read in bounded windows. Lists provide pagination. Ask your client to use a commit SHA for a consistent file view. Binary files, symlinks and submodules are not fetched as text, and external download links are not followed.

The MCP does not edit files, push commits, merge pull requests, delete repositories, execute code or manage CI jobs. Use your normal Git workflow for those tasks. It never retries writes automatically: if a connection is lost during a write, check Gitza before asking the client to retry.

Troubleshooting and updates

  • Executable not found: check that gitza-mcp is on the client’s PATH, or configure the absolute path to the installed executable. Restart the client after changing its environment.
  • Missing token or access denied: check that the client inherits GITZA_TOKEN, that the token is still valid, and that both its repository restrictions and GITZA_REPOSITORIES include the requested owner/name.
  • Writes refused: local connections require GITZA_WRITE=true and the write token scopes. Hosted connections require write permission in the consent grant.
  • Hosted connection stopped working: check your current Gitza repository access and reconnect if the grant was revoked or expired. Check that the endpoint is https://mcp.gitza.co.za/mcp and sign in again using claude mcp login gitza.

Before upgrading, read the release guide and tested client matrix . Claude Code 2.1.310 has been checked with local stdio and hosted browser login. Hosted OAuth, token refresh, repository reads and revocation have also passed production checks. MCP Inspector 2.12.0 and the official SDK client 1.32.2 were verified locally. Windows and other GUI clients have not been tested.

Report reproducible problems through the MCP issue tracker . Include your MCP and client versions, transport and redacted error message. Never include tokens, private repository contents or database credentials.