How to Use the Gitea MCP in VS Code Copilot

Q: Can my entire team share one Gitea setup in VS Code Copilot?

Yes, by saving the Gitea MCP server configuration to .vscode/mcp.json in your repository. When team members open the project in VS Code, Copilot automatically connects to Gitea using their configured tokens to run listrepos.

Q: Does the VS Code Copilot MCP server support Gitea organization management?

It does, using read-focused tools. Copilot can execute listorgs and getorg to inspect your Gitea organization structures directly from the chat interface.

Q: Can VS Code Copilot list branches on massive Gitea repositories?

Yes, Copilot runs listbranches efficiently by requesting paginated data from your Gitea instance. This ensures your editor stays responsive even when dealing with thousands of active branches.

Bring Gitea repository tracking and issue management directly into your VS Code Copilot chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gitea MCP to VS Code Copilot

Create your Vinkius account to connect Gitea to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Gitea with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-wide Gitea integration via VS Code Copilot

Share your Gitea MCP server configuration across your entire engineering team in VS Code Copilot by committing a single file. VS Code Copilot reads your `.vscode/mcp.json` file, granting every developer instant access to Gitea `list_repos` and `get_repo` without individual manual setups. This team-wide approach ensures everyone in VS Code Copilot works with the same Gitea repository metadata. Your developers can verify Gitea default branches and clone URLs directly within VS Code Copilot.

Inspect Gitea issues and pull requests inside VS Code

Avoid context switching by bringing Gitea issue tracking into your VS Code Copilot Chat interface. VS Code Copilot runs `list_issues` and `get_issue` to let you read Gitea bug descriptions side-by-side with your source code. Tracking active Gitea review cycles in VS Code Copilot Chat is just as simple. Checking pending Gitea pull requests with `list_pulls` helps the VS Code Copilot assistant prioritize code reviews without opening a web browser.

Map Gitea organization structures in VS Code Copilot

Managing enterprise Gitea repositories in VS Code Copilot requires clear visibility into team permissions and organization trees. VS Code Copilot executes `list_orgs` and `list_org_repos` to help you find where specific Gitea microservices live. Getting Gitea details inside VS Code Copilot Chat is straightforward. Running `get_org` and checking active development paths via `list_branches` allows the VS Code Copilot agent to ensure your team's code lands in the correct Gitea repository.

Setup guide

Set up Gitea MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Gitea MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Gitea tools listed. Try asking: "List my recent Gitea transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gitea. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Gitea now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Gitea MCP in VS Code Copilot

Yes, by saving the Gitea MCP server configuration to `.vscode/mcp.json` in your repository. When team members open the project in VS Code, Copilot automatically connects to Gitea using their configured tokens to run `list_repos`.

It does, using read-focused tools. Copilot can execute `list_orgs` and `get_org` to inspect your Gitea organization structures directly from the chat interface.

You authenticate by setting your Gitea token in your VS Code user settings or environment variables. The Copilot agent uses this token to run `get_me` and verify your identity before accessing repository data.

Yes, Copilot runs `list_branches` efficiently by requesting paginated data from your Gitea instance. This ensures your editor stays responsive even when dealing with thousands of active branches.

Your Gitea repository metadata, issues, and pull request details are fetched over an encrypted connection managed by Vinkius. The MCP server runs in a secure, isolated sandbox, meaning your Gitea data isn't cached or used for model training.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript