personal-projects/gitea-mcp-remote
1
0
Fork 0
generated from personal-projects/leo-claude-mktplace
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 02] setup: Create correct directory structure and dependencies #10

New Issue
Closed
opened 2026-02-03 21:00:31 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-02-03 21:00:31 +00:00
Owner
Copy Link

Summary

Set up the correct package structure (src/gitea_mcp_remote/) and rewrite pyproject.toml to depend on the marketplace package.

Tasks

  • Create src/gitea_mcp_remote/ directory (note: underscore, not hyphen)
  • Create src/gitea_mcp_remote/__init__.py
  • Rewrite pyproject.toml with:
    • Correct package name: gitea-mcp-remote
    • Dependency on gitea-mcp-server (marketplace package)
    • Dependencies: mcp, httpx, python-dotenv, pydantic
    • Entry point for HTTP server: gitea-mcp-remote = gitea_mcp_remote.server_http:main
  • Verify structure with tree src/

Acceptance Criteria

  • src/gitea_mcp_remote/ exists with __init__.py
  • pyproject.toml has correct package name and marketplace dependency
  • pyproject.toml includes all required dependencies
  • Entry point configured for HTTP server
  • Project metadata updated (description, authors, etc.)

Dependencies

Blocked by: #9 (cleanup must complete first)

Context

This is a deployment wrapper, not a standalone server. It imports tools from the marketplace package and adds deployment-specific logic (filtering, auth, HTTP transport).

References:

  • Corrective Rebuild specification
  • Steps 2-3 of 14-step rebuild plan

Size: S (1-2 hours)

## Summary Set up the correct package structure (`src/gitea_mcp_remote/`) and rewrite `pyproject.toml` to depend on the marketplace package. ## Tasks - [ ] Create `src/gitea_mcp_remote/` directory (note: underscore, not hyphen) - [ ] Create `src/gitea_mcp_remote/__init__.py` - [ ] Rewrite `pyproject.toml` with: - Correct package name: `gitea-mcp-remote` - Dependency on `gitea-mcp-server` (marketplace package) - Dependencies: `mcp`, `httpx`, `python-dotenv`, `pydantic` - Entry point for HTTP server: `gitea-mcp-remote = gitea_mcp_remote.server_http:main` - [ ] Verify structure with `tree src/` ## Acceptance Criteria - `src/gitea_mcp_remote/` exists with `__init__.py` - `pyproject.toml` has correct package name and marketplace dependency - `pyproject.toml` includes all required dependencies - Entry point configured for HTTP server - Project metadata updated (description, authors, etc.) ## Dependencies **Blocked by:** #9 (cleanup must complete first) ## Context This is a deployment wrapper, not a standalone server. It imports tools from the marketplace package and adds deployment-specific logic (filtering, auth, HTTP transport). **References:** - Corrective Rebuild specification - Steps 2-3 of 14-step rebuild plan **Size:** S (1-2 hours)
lmiranda added this to the Sprint 02: Corrective Rebuild milestone 2026-02-03 21:00:31 +00:00
lmiranda added the Tech/PythonType/SetupComponent/BackendPriority/HighSize/S labels 2026-02-03 21:00:31 +00:00
lmiranda commented 2026-02-03 21:00:36 +00:00
Author
Owner
Copy Link

⚠️ Blocked By: #9

⚠️ **Blocked By:** #9
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend/server-side code
 Component/Backend
Backend service code and business logic
 Component/Core
Core application logic and architecture
 Component/Database
Database schemas, migrations, queries
 Component/Dependencies
Package dependencies and requirements
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docker
Docker and containerization
 Component/Docs
Documentation and guides
 Component/Documentation
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Integration
Integration and end-to-end testing
 Component/Testing
Test infrastructure and frameworks
 Priority/Critical
Critical priority - blocks other work
 Priority/High
High priority items
 Priority/Medium
Medium priority items
 Size/L
Large task (4-8 hours)
 Size/M
Medium task (2-4 hours)
 Size/S
Small task (1-2 hours)
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
 Type/Build
Build system and dependencies
 Type/Documentation
Documentation updates
 Type/Feature
New feature implementation
 Type/Refactor
Code refactoring and restructuring
 Type/Setup
Initial project setup tasks
 Type/Test
Testing and quality assurance
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Backend Priority/High Size/S Tech/Python Type/Setup
Milestone
No items
No Milestone Sprint 02: Corrective Rebuild
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/gitea-mcp-remote#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?