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.

Gitea MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Gitea
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Gitea and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitea": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Gitea MCP Server

Connect your Gitea instance to any AI agent and take full control of your self-hosted Git services, code reviews, and project collaboration through natural conversation.

GitHub Copilot Agent mode brings Gitea data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Repository Orchestration — List all accessible repositories and retrieve full details including descriptions, clone URLs, stars, and visibility states natively
Issue & Task Tracking — Enumerate issues in any repository to track numbers, states, labels, and assignees, and retrieve full body content for detailed analysis flawlessly
Pull Request Auditing — List all pull requests to monitor open, closed, or merged states and review source/target branch mappings synchronously
Organization Management — Identify organizations you belong to and retrieve detailed org metadata including website, location, and repository counts securely
Branch & Protection Oversight — List all branches in a repository and verify commit SHAs and effective branch protection rules natively
User Profile Discovery — Extract the authenticated profile identity including login, email, full name, and administrative status flawlessy
Project Navigation — Analyze specific localized variables decoding active data routes and extracting hidden structural constraints within your Gitea environment

The Gitea MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Gitea to VS Code Copilot via MCP

Follow these steps to integrate the Gitea MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Gitea

Ask Copilot: "Using Gitea, help me...". 10 tools available

Why Use VS Code Copilot with the Gitea MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Gitea through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Gitea + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Gitea MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Gitea MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Gitea to VS Code Copilot via MCP:

get_issue

Get full details of a Gitea issue

get_me

Get the authenticated Gitea user profile

get_org

Get full details of a Gitea organization

get_repo

Get full details of a Gitea repository

list_branches

List all branches in a Gitea repository

list_issues

List all issues in a Gitea repository

list_org_repos

List all repositories belonging to a Gitea organization

list_orgs

List all organizations the authenticated Gitea user belongs to

list_pulls

List all pull requests in a Gitea repository

list_repos

Returns repo full names, descriptions, clone URLs, stars, forks, private/public status, and default branches. List all repositories accessible to the authenticated Gitea user

Example Prompts for Gitea in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Gitea immediately.

"List the last 5 repositories I worked on"

"Show me open pull requests for repo 'api-service'"

"List all issues in organization 'Eng-Team'"

Troubleshooting Gitea MCP Server with VS Code Copilot

Common issues when connecting Gitea to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Gitea + VS Code Copilot FAQ

Common questions about integrating Gitea MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.