4,000+ servers built on vurb.ts
Vinkius

Forgejo (Gitea Fork) MCP Server for ClineGive Cline instant access to 4 tools to Create Token, Dispatch Workflow, Get Forgejo Version, and more

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Forgejo (Gitea Fork) through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The Forgejo (Gitea Fork) MCP Server for Cline is a standout in the Loved By Devs category — giving your AI agent 4 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "forgejo-gitea-fork": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Forgejo (Gitea Fork)
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 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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Forgejo (Gitea Fork) tool calls without waiting for prompts between steps. Connect 4 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline

When Cline 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

Create token on Forgejo (Gitea Fork)

Generates a new personal access token. Generate a new API token for a user

dispatch

Dispatch workflow on Forgejo (Gitea Fork)

Trigger a manual workflow dispatch in Forgejo Actions

get

Get forgejo version on Forgejo (Gitea Fork)

Get detailed Forgejo version information

get

Get gitea version on Forgejo (Gitea Fork)

Get the Gitea-compatible version of the Forgejo instance

Connect Forgejo (Gitea Fork) to Cline via MCP

Follow these steps to wire Forgejo (Gitea Fork) into Cline. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using Forgejo (Gitea Fork)

Ask Cline: "Using Forgejo (Gitea Fork), help me...". 4 tools available

Why Use Cline with the Forgejo (Gitea Fork) MCP Server

Cline provides unique advantages when paired with Forgejo (Gitea Fork) through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Forgejo (Gitea Fork) + Cline Use Cases

Practical scenarios where Cline combined with the Forgejo (Gitea Fork) MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from Forgejo (Gitea Fork) and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Forgejo (Gitea Fork) tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Forgejo (Gitea Fork) and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Forgejo (Gitea Fork) for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Forgejo (Gitea Fork) in Cline

Ready-to-use prompts you can give your Cline agent to start working with Forgejo (Gitea Fork) immediately.

01

"Check the Forgejo and Gitea-compatible versions of my instance."

02

"Generate a new API token named 'CI-Runner' with read:repository scope for user 'admin'."

03

"Trigger the 'deploy.yaml' workflow in the 'main-app' repository owned by 'dev-team'."

Troubleshooting Forgejo (Gitea Fork) MCP Server with Cline

Common issues when connecting Forgejo (Gitea Fork) to Cline through Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Forgejo (Gitea Fork) + Cline FAQ

Common questions about integrating Forgejo (Gitea Fork) MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →