Forgejo (Gitea Fork) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 4 tools to Create Token, Dispatch Workflow, Get Forgejo Version, and more
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.
Ask AI about this MCP Server for VS Code Copilot
The Forgejo (Gitea Fork) MCP Server for VS Code Copilot is a standout in the Loved By Devs category — giving your AI agent 4 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
{
"mcpServers": {
"forgejo-gitea-fork": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Forgejo (Gitea Fork) and 4,000+ MCP Servers from a single visual interface.





* 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 Forgejo (Gitea Fork) MCP Server
Connect your Forgejo or Gitea instance to any AI agent to streamline your DevOps and repository management workflows through natural conversation.
GitHub Copilot Agent mode brings Forgejo (Gitea Fork) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Version Auditing — Retrieve detailed Forgejo and Gitea-compatible version information to ensure API compatibility across your infrastructure.
- Token Management — Generate new Personal Access Tokens (PATs) with specific scopes (read/write) using your BasicAuth credentials.
- CI/CD Automation — Trigger manual workflow dispatches for Forgejo Actions directly from the chat to start builds or deployments.
- Instance Inspection — Verify the health and configuration of your self-hosted Git service without leaving your development environment.
The Forgejo (Gitea Fork) MCP Server exposes 4 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 4 Forgejo (Gitea Fork) tools available for VS Code Copilot
When VS Code Copilot connects to Forgejo (Gitea Fork) through Vinkius, your AI agent gets direct access to every tool listed below — spanning git-repository, self-hosted, version-control, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Create token on Forgejo (Gitea Fork)
Generates a new personal access token. Generate a new API token for a user
Dispatch workflow on Forgejo (Gitea Fork)
Trigger a manual workflow dispatch in Forgejo Actions
Get forgejo version on Forgejo (Gitea Fork)
Get detailed Forgejo version information
Get gitea version on Forgejo (Gitea Fork)
Get the Gitea-compatible version of the Forgejo instance
Connect Forgejo (Gitea Fork) to VS Code Copilot via MCP
Follow these steps to wire Forgejo (Gitea Fork) into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Forgejo (Gitea Fork)
Why Use VS Code Copilot with the Forgejo (Gitea Fork) MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Forgejo (Gitea Fork) 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
Forgejo (Gitea Fork) + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Forgejo (Gitea Fork) 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
Example Prompts for Forgejo (Gitea Fork) in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Forgejo (Gitea Fork) immediately.
"Check the Forgejo and Gitea-compatible versions of my instance."
"Generate a new API token named 'CI-Runner' with read:repository scope for user 'admin'."
"Trigger the 'deploy.yaml' workflow in the 'main-app' repository owned by 'dev-team'."
Troubleshooting Forgejo (Gitea Fork) MCP Server with VS Code Copilot
Common issues when connecting Forgejo (Gitea Fork) to VS Code Copilot through Vinkius, and how to resolve them.
MCP tools not available
Forgejo (Gitea Fork) + VS Code Copilot FAQ
Common questions about integrating Forgejo (Gitea Fork) MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.Explore More MCP Servers
View all →
Humanitix
10 toolsManage events, tickets, and attendees via Humanitix API.

Airwallex
6 toolsProcess global payments, manage multi-currency accounts, and track international transfers with enterprise-grade treasury tools.

AI21 Studio
7 toolsUnlock AI21's Jamba models and language tools for summarizing, paraphrasing, and grammar correction natively.

Object Hash Engine
1 toolsGenerate deterministic SHA-256 fingerprints of any JSON object. Keys are automatically sorted so {b:2,a:1} and {a:1,b:2} always produce the exact same hash. Essential for deduplication.
