gitea-mcp 0.1.1.dev0__tar.gz

gitea_mcp-0.1.1.dev0/.github/pull_request_template.md

@@ -0,0 +1,66 @@
+## Summary
+
+Describe the change and why it is needed.
+
+## What Changed
+
+- 
+- 
+- 
+
+## Type of Change
+
+- [ ] Bug fix (PATCH)
+- [ ] New feature (MINOR)
+- [ ] Breaking change (MAJOR)
+- [ ] Documentation only
+- [ ] Tests only
+- [ ] Refactor/internal change
+
+## Changelog
+
+- [ ] I updated `CHANGELOG.md` under `[Unreleased]`
+- [ ] No changelog update needed (explain why):
+
+## Versioning Impact
+
+Expected release impact (pick one):
+
+- [ ] PATCH
+- [ ] MINOR
+- [ ] MAJOR
+- [ ] None
+
+Notes:
+
+## Testing
+
+List what you ran and key results.
+
+```bash
+pytest
+```
+
+Optional additional checks:
+
+```bash
+ruff check .
+mypy
+```
+
+## MCP / API Considerations
+
+- [ ] Tool names unchanged
+- [ ] Tool parameter names unchanged
+- [ ] Response shape unchanged
+- [ ] Any breaking MCP/API behavior is documented above
+
+## Manual Validation (if applicable)
+
+- Gitea/Forgejo/Codeberg target tested:
+- Example endpoint(s) exercised:
+- Auth scope validation performed:
+
+## Related Issues
+
+Closes #

gitea_mcp-0.1.1.dev0/.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # setuptools_scm needs full history for version derivation
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+
+      - name: Lint (ruff)
+        run: ruff check .
+
+      - name: Type check (mypy)
+        run: mypy src
+
+      - name: Test (pytest)
+        run: pytest

gitea_mcp-0.1.1.dev0/.github/workflows/release.yml

@@ -0,0 +1,34 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write  # required for PyPI trusted publishing
+      contents: read
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # setuptools_scm needs full history
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: |
+          python -m pip install --upgrade pip
+          pip install build
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

gitea_mcp-0.1.1.dev0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

gitea_mcp-0.1.1.dev0/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+- Initial project scaffolding.
+- **Issue tools fully implemented:** `create_issue`, `list_issues`, `get_issue`, `update_issue`, `add_comment`. Label names are resolved to Gitea label IDs automatically (Gitea's issue API requires IDs, not names); unknown label names fail cleanly with the list of valid names. `get_issue` returns the issue object plus a `comments_list` field with the full comment thread. `update_issue` supports replace-semantics for labels and assignees, milestone clearing via `milestone=0`, and atomic partial updates of any combination of title/body/state/labels/assignees/milestone.
+- **Repo metadata tools fully implemented:** `list_repos`, `list_labels`, `list_milestones`. `list_repos` handles three modes — authenticated-user (no owner), user-owned, or organization-owned — with automatic fallback from the user endpoint to the org endpoint on 404 so callers don't need to know which it is. `list_labels` and `list_milestones` are straightforward paginated reads.
+- **Release tools fully implemented:** `list_releases`, `create_release`. `create_release` includes a warning in its docstring about Gitea's side-effect behavior of creating the underlying git tag even for drafts. All MVP fields supported: `tag_name`, `name`, `body`, `target_commitish`, `draft`, `prerelease`.
+- `GiteaClient` async HTTP wrapper (PAT auth via `Authorization: token <PAT>`, httpx, raises typed errors). Supports GET, POST, PUT, PATCH, DELETE.
+- `Config` dataclass loading from `GITEA_URL` / `GITEA_TOKEN` / `GITEA_TIMEOUT` environment variables.
+- `gitea-mcp` console-script entry point.
+- `setuptools_scm` tag-driven versioning.
+- `mcp.json` template for MCP client configuration.
+- `README.md` with quick start, configuration, and tool reference.
+- `VERSIONING.md` documenting the semver / tag / release flow.
+- GitHub Actions workflows: CI (lint + type-check + tests on Python 3.11/3.12/3.13) and Release (publish to PyPI on `v*` tag push).
+- Unit test suite using `pytest-httpx` to mock the Gitea API. Issue tools have full coverage (12 tests); repo and release tools covered only by smoke tests pending Pass B-2/B-3.

gitea_mcp-0.1.1.dev0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Sam Ware
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

gitea_mcp-0.1.1.dev0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: gitea-mcp
+Version: 0.1.1.dev0
+Summary: Model Context Protocol server for Gitea (and Forgejo, Codeberg).
+Author-email: Sam Ware <samuel@waretech.services>
+License: MIT
+Project-URL: Homepage, https://github.com/werebear73/gitea-mcp
+Project-URL: Issues, https://github.com/werebear73/gitea-mcp/issues
+Project-URL: Source, https://github.com/werebear73/gitea-mcp
+Keywords: mcp,gitea,forgejo,codeberg,model-context-protocol,llm,ai
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Version Control :: Git
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: fastmcp>=2.0.0
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: pydantic>=2.0.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: pytest-httpx>=0.30; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Dynamic: license-file
+
+# gitea-mcp
+
+A [Model Context Protocol](https://modelcontextprotocol.io) server for [Gitea](https://gitea.io) — lets AI assistants (Claude, ChatGPT, Copilot, and anything else that speaks MCP) read, create, and manage issues, repositories, and releases on any Gitea instance you can reach.
+
+Also works against **[Forgejo](https://forgejo.org)** and **[Codeberg](https://codeberg.org)** (API-compatible).
+
+## Why
+
+Self-hosted Gitea is a popular GitHub alternative for solo developers, small teams, and privacy-conscious organizations. With this MCP server installed, your AI assistant can:
+
+- File audit findings or refactor notes as Gitea issues without you leaving the chat
+- Triage a repo's open issues in natural language
+- Cut a release at the end of a coding session
+- Comment on issues across multiple repos in one pass
+
+## Features
+
+| Resource | Tools |
+| --- | --- |
+| Issues | `create_issue`, `list_issues`, `get_issue`, `update_issue`, `add_comment` |
+| Repos | `list_repos`, `list_labels`, `list_milestones` |
+| Releases | `list_releases`, `create_release` |
+
+- Bearer authentication via Personal Access Token (PAT)
+- Async HTTP via `httpx` and `FastMCP`
+- Works with self-hosted Gitea, Forgejo, and Codeberg
+
+## Quick Start
+
+### 1. Install
+
+```bash
+pip install gitea-mcp
+```
+
+Or with [`uv`](https://docs.astral.sh/uv/):
+
+```bash
+uv pip install gitea-mcp
+```
+
+### 2. Generate a Personal Access Token
+
+In your Gitea instance, go to **Settings → Applications → Generate New Token** and grant at least:
+
+- `read:repository`
+- `write:issue`
+- `read:user`
+
+Add `write:repository` if you also want to create releases.
+
+### 3. Configure your MCP client
+
+Add `gitea-mcp` to your MCP client configuration:
+
+```json
+{
+  "mcpServers": {
+    "gitea": {
+      "command": "gitea-mcp",
+      "env": {
+        "GITEA_URL": "https://your-gitea-instance.example.com",
+        "GITEA_TOKEN": "your-personal-access-token"
+      }
+    }
+  }
+}
+```
+
+See [`mcp.json`](mcp.json) for a complete example. The same shape works for Claude Desktop, VS Code, Cowork, Claude Code, and any other MCP-compatible client.
+
+## Configuration
+
+Configuration is read from environment variables.
+
+| Variable | Required | Default | Description |
+| --- | --- | --- | --- |
+| `GITEA_URL` | Yes | — | Base URL of your Gitea instance (e.g., `https://gitea.example.com`) |
+| `GITEA_TOKEN` | Yes | — | Personal Access Token from your Gitea user settings |
+| `GITEA_TIMEOUT` | No | `30` | HTTP request timeout in seconds |
+
+## Compatibility
+
+| Server | Status |
+| --- | --- |
+| Gitea (self-hosted) | ✅ Primary target |
+| Forgejo | ✅ Expected to work (API-compatible) |
+| Codeberg | ✅ Expected to work (Codeberg runs Forgejo) |
+
+## Development
+
+```bash
+git clone https://github.com/werebear73/gitea-mcp.git
+cd gitea-mcp
+pip install -e ".[dev]"
+pytest
+```
+
+## Versioning
+
+Semantic versioning, derived from git tags via `setuptools_scm`. See [`VERSIONING.md`](VERSIONING.md) for the release process.
+
+## Contributing
+
+Issues and pull requests welcome. For substantial changes, please open an issue first to discuss the approach.
+
+## License
+
+[MIT](LICENSE) — use it however you like, including commercial products.
+
+---
+
+Built by [Waretech Services](https://waretech.services).

gitea_mcp-0.1.1.dev0/README.md

@@ -0,0 +1,113 @@
+# gitea-mcp
+
+A [Model Context Protocol](https://modelcontextprotocol.io) server for [Gitea](https://gitea.io) — lets AI assistants (Claude, ChatGPT, Copilot, and anything else that speaks MCP) read, create, and manage issues, repositories, and releases on any Gitea instance you can reach.
+
+Also works against **[Forgejo](https://forgejo.org)** and **[Codeberg](https://codeberg.org)** (API-compatible).
+
+## Why
+
+Self-hosted Gitea is a popular GitHub alternative for solo developers, small teams, and privacy-conscious organizations. With this MCP server installed, your AI assistant can:
+
+- File audit findings or refactor notes as Gitea issues without you leaving the chat
+- Triage a repo's open issues in natural language
+- Cut a release at the end of a coding session
+- Comment on issues across multiple repos in one pass
+
+## Features
+
+| Resource | Tools |
+| --- | --- |
+| Issues | `create_issue`, `list_issues`, `get_issue`, `update_issue`, `add_comment` |
+| Repos | `list_repos`, `list_labels`, `list_milestones` |
+| Releases | `list_releases`, `create_release` |
+
+- Bearer authentication via Personal Access Token (PAT)
+- Async HTTP via `httpx` and `FastMCP`
+- Works with self-hosted Gitea, Forgejo, and Codeberg
+
+## Quick Start
+
+### 1. Install
+
+```bash
+pip install gitea-mcp
+```
+
+Or with [`uv`](https://docs.astral.sh/uv/):
+
+```bash
+uv pip install gitea-mcp
+```
+
+### 2. Generate a Personal Access Token
+
+In your Gitea instance, go to **Settings → Applications → Generate New Token** and grant at least:
+
+- `read:repository`
+- `write:issue`
+- `read:user`
+
+Add `write:repository` if you also want to create releases.
+
+### 3. Configure your MCP client
+
+Add `gitea-mcp` to your MCP client configuration:
+
+```json
+{
+  "mcpServers": {
+    "gitea": {
+      "command": "gitea-mcp",
+      "env": {
+        "GITEA_URL": "https://your-gitea-instance.example.com",
+        "GITEA_TOKEN": "your-personal-access-token"
+      }
+    }
+  }
+}
+```
+
+See [`mcp.json`](mcp.json) for a complete example. The same shape works for Claude Desktop, VS Code, Cowork, Claude Code, and any other MCP-compatible client.
+
+## Configuration
+
+Configuration is read from environment variables.
+
+| Variable | Required | Default | Description |
+| --- | --- | --- | --- |
+| `GITEA_URL` | Yes | — | Base URL of your Gitea instance (e.g., `https://gitea.example.com`) |
+| `GITEA_TOKEN` | Yes | — | Personal Access Token from your Gitea user settings |
+| `GITEA_TIMEOUT` | No | `30` | HTTP request timeout in seconds |
+
+## Compatibility
+
+| Server | Status |
+| --- | --- |
+| Gitea (self-hosted) | ✅ Primary target |
+| Forgejo | ✅ Expected to work (API-compatible) |
+| Codeberg | ✅ Expected to work (Codeberg runs Forgejo) |
+
+## Development
+
+```bash
+git clone https://github.com/werebear73/gitea-mcp.git
+cd gitea-mcp
+pip install -e ".[dev]"
+pytest
+```
+
+## Versioning
+
+Semantic versioning, derived from git tags via `setuptools_scm`. See [`VERSIONING.md`](VERSIONING.md) for the release process.
+
+## Contributing
+
+Issues and pull requests welcome. For substantial changes, please open an issue first to discuss the approach.
+
+## License
+
+[MIT](LICENSE) — use it however you like, including commercial products.
+
+---
+
+Built by [Waretech Services](https://waretech.services).