2 Commits

Author	SHA1	Message	Date
lmiranda	184ab48933	fix(gitea): standardize build backend to setuptools ... Replace hatchling with setuptools to match all other MCP servers (contract-validator, viz-platform, data-platform). Changes: - build-system: hatchling → setuptools>=61.0 - license: string → PEP 639 format {text = "MIT"} - Remove redundant License classifier - Add [tool.setuptools.packages.find] config - Add [tool.pytest.ini_options] for consistency Verified: pip install -e . succeeds, 36 tools registered, 64 tests pass. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-03 15:05:56 -05:00
lmiranda	c37107fc42	feat(gitea): add pip-installable packaging for external consumption ... Extract tool definitions and dispatcher from server.py into tool_registry.py to enable transport-agnostic reuse. External consumers (e.g., HTTP transport in gitea-mcp-remote) can now import and use the Gitea MCP tools without duplicating code. Changes: - Create pyproject.toml with PEP 621 compliant package manifest (hatchling) - Create tool_registry.py with get_tool_definitions() and create_tool_dispatcher() - Refactor server.py to use registry (1100 -> 93 lines) - Update __init__.py with package exports and __version__ The tool_filter parameter enables selective tool exposure for remote servers. Stdio transport behavior is unchanged - all 36 tools still work identically. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-02-03 13:57:59 -05:00