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

Name: Forgejo (Gitea Fork)
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

Open in ChatGPT Open in Claude Open in Perplexity

The Forgejo (Gitea Fork) MCP Server for Cursor 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

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ 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.

Download Free Open SourceNo signup required

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.

Cursor's Agent mode turns Forgejo (Gitea Fork) into an in-editor superpower. Ask Cursor to generate code using live data from Forgejo (Gitea Fork) and it fetches, processes, and writes. all in a single agentic loop. 4 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

When Cursor 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 Cursor via MCP

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Forgejo (Gitea Fork)

Open Agent mode in chat and ask: "Using Forgejo (Gitea Fork), help me...". 4 tools available

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

Cursor AI Code Editor provides unique advantages when paired with Forgejo (Gitea Fork) through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Forgejo (Gitea Fork) + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Forgejo (Gitea Fork) in Cursor

Ready-to-use prompts you can give your Cursor 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 Cursor

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Forgejo (Gitea Fork) + Cursor FAQ

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

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.