[Sprint 01] feat: Implement Gitea issue operations tools #3

Closed
opened 2026-02-03 19:40:24 +00:00 by lmiranda · 2 comments
Owner

Implement MCP tools for Gitea issue operations (list, get, create, update).

Acceptance Criteria:

  • Implement gitea_list_issues with filters (state, labels, milestone, page)
  • Implement gitea_get_issue(issue_number)
  • Implement gitea_create_issue(title, body, labels[], milestone, assignees[])
  • Implement gitea_update_issue(issue_number, state, title, body, labels[], assignees[])
  • Proper error handling for 404, 401, 403 responses
  • Return structured data matching MCP tool response format

Gitea API Endpoints:

  • GET /repos/{owner}/{repo}/issues
  • GET /repos/{owner}/{repo}/issues/{index}
  • POST /repos/{owner}/{repo}/issues
  • PATCH /repos/{owner}/{repo}/issues/{index}

Blocked By: #2

Implement MCP tools for Gitea issue operations (list, get, create, update). **Acceptance Criteria:** - [ ] Implement gitea_list_issues with filters (state, labels, milestone, page) - [ ] Implement gitea_get_issue(issue_number) - [ ] Implement gitea_create_issue(title, body, labels[], milestone, assignees[]) - [ ] Implement gitea_update_issue(issue_number, state, title, body, labels[], assignees[]) - [ ] Proper error handling for 404, 401, 403 responses - [ ] Return structured data matching MCP tool response format **Gitea API Endpoints:** - GET /repos/{owner}/{repo}/issues - GET /repos/{owner}/{repo}/issues/{index} - POST /repos/{owner}/{repo}/issues - PATCH /repos/{owner}/{repo}/issues/{index} **Blocked By:** #2
Author
Owner

⚠️ Blocked By: #2

⚠️ **Blocked By:** #2
Author
Owner

✓ Implementation complete on branch feat/3-issue-tools

Completed:

  • Implemented gitea_list_issues with filters (state, labels, milestone, page)
  • Implemented gitea_get_issue(issue_number) for single issue retrieval
  • Implemented gitea_create_issue(title, body, labels, milestone, assignees)
  • Implemented gitea_update_issue(issue_number, state, title, body, labels, assignees)
  • Added proper error handling for 404, 401, 403 responses
  • Return structured data matching MCP tool response format

Gitea API Endpoints Used:

  • GET /repos/{owner}/{repo}/issues
  • GET /repos/{owner}/{repo}/issues/{index}
  • POST /repos/{owner}/{repo}/issues
  • PATCH /repos/{owner}/{repo}/issues/{index}

Files Created:

  • src/gitea_mcp/tools/issues.py

All acceptance criteria met. Issue operations tools ready for use.

✓ Implementation complete on branch `feat/3-issue-tools` ## Completed: - Implemented gitea_list_issues with filters (state, labels, milestone, page) - Implemented gitea_get_issue(issue_number) for single issue retrieval - Implemented gitea_create_issue(title, body, labels, milestone, assignees) - Implemented gitea_update_issue(issue_number, state, title, body, labels, assignees) - Added proper error handling for 404, 401, 403 responses - Return structured data matching MCP tool response format ## Gitea API Endpoints Used: - GET /repos/{owner}/{repo}/issues - GET /repos/{owner}/{repo}/issues/{index} - POST /repos/{owner}/{repo}/issues - PATCH /repos/{owner}/{repo}/issues/{index} ## Files Created: - src/gitea_mcp/tools/issues.py All acceptance criteria met. Issue operations tools ready for use.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/gitea-mcp-remote#3