# Gitea MCP for AI Agents AI Agent Connect > Gitea lets you manage your self-hosted Git service directly through your AI agent. You can list repositories, track issues and pull requests, and handle organization metadata without switching tabs. It connects your private code hosting environment to your workflow, making it easy to audit branches and monitor project progress in real-time. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_SICQZKEcHwUlk0yUptygSAxtaKOlo84McxfBfExb/ai-agent-connect - **Tags:** git, version-control, self-hosted, code-hosting, issue-tracking ## Description Managing a self-hosted Git instance usually feels like a chore. You spend your day jumping between browser tabs, searching for specific issue numbers, and manually checking which pull requests are still open. It is a lot of context switching that pulls you away from actually writing code or planning projects. This Connector changes that by giving your AI agent a direct line into your Gitea environment. Instead of manually searching for a specific pull request or checking if a branch is protected, you just ask your agent to do it for you. You can have your agent summarize recent activity, find specific tasks assigned to your team, or pull up organization details in seconds. It turns your code hosting platform into an interactive workspace where you can query your project's state naturally. When you find this in the Vinkius catalog, you are getting a way to bridge the gap between your private infrastructure and your daily communication tools. It is about moving from clicking buttons to getting answers. ## Tools ### list_issues List every issue within a repository. Use this to get a high-level view of what needs to be fixed. ### get_issue Retrieve the full body and metadata for one issue. This is great for reading detailed bug reports or tasks. ### list_orgs See all organizations you belong to. It makes it easy to navigate between different team workspaces. ### get_org Get the full metadata for a specific organization. You can check out website links and repository counts. ### list_pulls List all pull requests in a repository. This lets you monitor what is currently being merged or reviewed. ### list_branches List all branches in a repository. It helps you verify which branches are active or need attention. ### get_me Get your own authenticated user profile. This lets the agent know your login details and admin status. ### list_repos List all repositories accessible to your user. This gives a quick overview of your entire workspace. ### get_repo Get the full details of a specific Gitea repository. This helps you see descriptions and clone URLs quickly. ### list_org_repos List all repositories that belong to a specific organization. Use this to see what a whole team is working on. ## Prompt Examples **Prompt:** ``` What are the most recent issues in the 'frontend-app' repo? ``` **Response:** ``` Checking the issues for **frontend-app**... I found the following active issues: | ID | Status | Label | Assignee | |---|---|---|---| | #104 | Open | Bug | @dev_user | | #105 | Open | Task | @lead_dev | | #106 | Closed | Bug | @dev_user | Would you like me to pull the full description for #104? ``` **Prompt:** ``` Show me all the organizations I'm part of and how many repos they have. ``` **Response:** ``` Retrieving your organization memberships... You belong to the following organizations: * **Eng-Team**: 42 repositories * **Design-Ops**: 12 repositories * **Infrastructure-Core**: 8 repositories Which team's repositories would you like to explore? ``` **Prompt:** ``` List all the open pull requests for the 'api-gateway' project. ``` **Response:** ``` Fetching pull requests for **api-gateway**... I found 3 open pull requests: * **#201**: Add OAuth support (Source: `feat/auth`) * **#202**: Fix rate-limiting bug (Source: `bugfix/rate-limit`) * **#205**: Update documentation (Source: `docs/update`) Do you want to see the branch mappings for any of these? ``` ## Capabilities ### List all accessible repositories See every project in your workspace at once using list_repos. ### Fetch specific repository details Get clone URLs and visibility states for a specific project with get_repo. ### Enumerate all issues in a project Pull a full list of tasks and bugs using list_issues. ### Retrieve full content for a single issue Read the entire body of a specific task with get_issue. ### View all pull requests in a repo Monitor what is currently being merged or reviewed with list_pulls. ### Identify organization memberships See which teams you belong to using list_orgs. ### Check branch protection rules Verify your branch security and commit SHAs with list_branches. ### Extract your personal user profile Get your own login details and admin status with get_me. ## Use Cases ### Reviewing pending pull requests A developer wants to see all open pull requests for a specific service to see what is ready for review. ### Tracking organization progress A product manager needs to list all issues in a specific organization to check progress on a new feature. ### Auditing branch security A DevOps lead wants to verify the branch protection rules for a production repository. ### Personal repository overview An indie hacker wants to see their own profile details and list all their private repositories at once. ## Benefits - Stop switching tabs by using list_repos to see your entire workspace in one place. - Get instant summaries of work with list_issues to see what is on the backlog. - Quickly audit code reviews by using list_pulls to see what is pending. - Verify security settings using list_branches to check branch protection rules. - Access organization metadata via list_orgs and get_org without searching through settings. - Identify your own permissions and profile details using get_me for faster troubleshooting. ## How It Works The bottom line is that you get a direct command line for your Git hosting via a chat interface. 1. Subscribe to the Gitea MCP on the Vinkius platform. 2. Enter your Gitea instance URL and your Access Token from your user settings. 3. Ask your AI client to list your repos or check issues to start working. ## Frequently Asked Questions **Can I use the Gitea MCP with my private self-hosted instance?** Yes, it is designed specifically for self-hosted Gitea. You just need to provide your instance URL and an access token. **Does the Gitea MCP work with Claude or Cursor?** Yes, it works with any MCP-compatible client like Claude, Cursor, and Windsurf. **Can I use this to manage issues and pull requests?** Yes, it lets your agent list, retrieve, and monitor issues and pull requests across your repositories. **Is my data safe with the Gitea MCP?** Since you are using your own Gitea instance, your data stays on your infrastructure. The Connector just provides the bridge for your agent to talk to it. **How do I get my Gitea access token?** You can find your token in your Gitea User Settings under the Applications section. **Can it see my organization's website and location?** Yes, it can retrieve organization metadata including the website and location using the get_org tool. **Can my agent list all issues in a Gitea repository?** Yes. Use the 'list_issues' tool. Provide the owner and repository name. The agent will return all issues with their titles, numbers, states, and labels, allowing you to monitor project progress natively. **How do I check the details of a specific pull request via chat?** Use the 'list_pulls' tool to see active PRs and their numbers. You can then ask for details about a specific PR to verify source/target branches and current review status synchronously. **Can I see all repositories belonging to a Gitea organization through the agent?** Absolutely. Use the 'list_org_repos' tool. Provide the organization name, and the agent will return all repositories belonging to that org, including their clone URLs and visibility status natively.