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 01] feat: Remove old server and create MCP base server structure #23

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

Delete old subprocess-based server and create new MCP HTTP server with marketplace imports and base structure.

Dependencies

Tasks

  • Delete src/gitea_mcp_remote/server.py
  • Create src/gitea_mcp_remote/server_http.py
  • Add imports from marketplace: from mcp_server import ...
  • Implement GiteaMCPServer class:
    • GiteaClient initialization with GiteaConfig
    • ToolFilter integration
    • Tool definitions loading
    • Tool dispatcher creation
  • Add startup/shutdown handlers
  • Create basic route structure
  • Keep health endpoints: /health, /healthz, /ping
  • Verify imports: from gitea_mcp_remote.server_http import GiteaMCPServer

Acceptance Criteria

  • Old server.py deleted
  • New server_http.py exists
  • Imports from marketplace mcp_server package
  • GiteaMCPServer class initialized with GiteaClient
  • Health endpoints functional
  • No subprocess spawning code
  • Can import server module successfully

Implementation Reference

See docs/sprint-proposals/sprint-01-implementation-guide.md - Phase 4, Issue #7-8 (Part 1)

Estimated Time: 2-3 hours

Note: This is part 1 of 2. Issue #24 will implement the MCP protocol endpoints.

Delete old subprocess-based server and create new MCP HTTP server with marketplace imports and base structure. ## Dependencies - Blocked by: #19, #20, #22 ## Tasks - [ ] Delete `src/gitea_mcp_remote/server.py` - [ ] Create `src/gitea_mcp_remote/server_http.py` - [ ] Add imports from marketplace: `from mcp_server import ...` - [ ] Implement GiteaMCPServer class: - GiteaClient initialization with GiteaConfig - ToolFilter integration - Tool definitions loading - Tool dispatcher creation - [ ] Add startup/shutdown handlers - [ ] Create basic route structure - [ ] Keep health endpoints: /health, /healthz, /ping - [ ] Verify imports: `from gitea_mcp_remote.server_http import GiteaMCPServer` ## Acceptance Criteria - Old `server.py` deleted - New `server_http.py` exists - Imports from marketplace `mcp_server` package - GiteaMCPServer class initialized with GiteaClient - Health endpoints functional - No subprocess spawning code - Can import server module successfully ## Implementation Reference See `docs/sprint-proposals/sprint-01-implementation-guide.md` - Phase 4, Issue #7-8 (Part 1) **Estimated Time:** 2-3 hours **Note:** This is part 1 of 2. Issue #24 will implement the MCP protocol endpoints.
lmiranda added this to the Sprint 01: Core Architecture Correction milestone 2026-02-03 22:50:44 +00:00
lmiranda added the Type/FeatureComponent/CoreSize/MPriority/Critical labels 2026-02-03 22:50:44 +00:00
lmiranda commented 2026-02-04 02:05:16 +00:00
Author
Owner
Copy Link

Completed and merged in commit 53a0006 (Merge feat/23: Remove old server and create MCP base server structure)

Completed and merged in commit 53a0006 (Merge feat/23: Remove old server and create MCP base server structure)
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/Core Priority/Critical Size/M Type/Feature
Milestone
No items
No Milestone Sprint 01: Core Architecture Correction
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#23
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?