How to Use the Forgejo (Gitea Fork) MCP in Windsurf

Q: How does Windsurf run Forgejo (Gitea Fork) workflows?

It uses the dispatchworkflow tool to send a manual trigger payload to your self-hosted instance. Cascade chains this tool with its file editing capabilities to write a fix and test it immediately.

Q: Can I use this server with Gitea instead of Forgejo?

Yes, it supports both. The server calls getgiteaversion to check API compatibility and ensure the tool commands match your specific instance.

Trigger workflows and manage access tokens right inside Windsurf using Cascade's autonomous multi-step execution.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Forgejo (Gitea Fork) MCP to Windsurf

Create your Vinkius account to connect Forgejo (Gitea Fork) to Windsurf 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 Forgejo (Gitea Fork) with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Forgejo Actions pipelines from Windsurf

This MCP Server exposes `dispatch_workflow` to let Windsurf kick off manual Actions runs on your Forgejo instance without you leaving the editor. Cascade reads your current workspace context, spots a failing build, and triggers a target workflow to test your fixes. You don't need to click around the Forgejo web UI to retry a run. Cascade handles the API payload behind the scenes, watches the dispatch trigger, and lets you focus on coding in Windsurf.

Provision API tokens directly in Windsurf

The `create_token` tool allows this MCP Server to generate personal access tokens for Forgejo directly inside your active Cascade session. Cascade can spin up a new token when a task requires authenticated API access to your self-hosted git instance. This keeps your master Forgejo credentials safe while letting the Windsurf agent provision short-lived, task-specific access. You get immediate API authorization for your repository without manual configuration overhead.

Verify API parity with version checks

This MCP Server uses `get_forgejo_version` and `get_gitea_version` to prevent compatibility errors before Cascade runs complex automation on your self-hosted git instance. Cascade checks these details to adapt its API requests depending on whether your setup runs Forgejo or upstream Gitea. This prevents unexpected failures when triggering workflows or managing repository resources inside Windsurf. Your agent knows exactly which API endpoints are safe to call before it writes a single line of integration code for your Gitea instance.

Setup guide

Set up Forgejo (Gitea Fork) MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Forgejo (Gitea Fork) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Forgejo (Gitea Fork) payment history." If connected, Cascade will call the Forgejo (Gitea Fork) tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "forgejo-gitea-fork-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 Forgejo. 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 Forgejo (Gitea Fork) 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 Forgejo (Gitea Fork) MCP in Windsurf

It uses the `dispatch_workflow` tool to send a manual trigger payload to your self-hosted instance. Cascade chains this tool with its file editing capabilities to write a fix and test it immediately.

Yes, it supports both. The server calls `get_gitea_version` to check API compatibility and ensure the tool commands match your specific instance.

No, Windsurf passes your configuration directly to the server running in Vinkius. Your API keys are kept in your local configuration file and never stored on our catalog.

Open your Windsurf settings, locate the Cascade MCP configuration, and insert the Vinkius server URL. Cascade will auto-discover the tools and let you trigger them with natural language.

This server handles your personal access tokens, repository metadata, and CI/CD workflow payloads. Vinkius runs the server in an isolated sandbox, meaning your raw credentials and Git data are never logged or exposed to other users.

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