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

Q: How do I install the Forgejo (Gitea Fork) integration in Claude Desktop?

Open your claudedesktopconfig.json file. Add the server details under the mcpServers key, save the file, and restart the app.

Control your self-hosted git infrastructure directly from Claude Desktop. Trigger builds and manage tokens without touching a terminal.

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 Claude Desktop

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger CI builds from your MCP Server

The `dispatch_workflow` tool lets Claude kick off manual Forgejo Actions runs. You tell your agent to deploy a staging build, and it fires the exact webhook needed to start the runner. This cuts out the browser entirely. Instead of clicking through repositories to find the right action, you just type the command. The agent handles the API request and confirms the job started.

Generate access credentials on the fly

The `create_token` tool issues fresh personal access tokens for specific users via this MCP Server. When you need a short-lived credential for a script, your agent provisions it immediately. Managing API keys usually means digging through settings menus. Right. So instead of doing that, you just ask Claude for a token, and it hands you a valid string ready for your environment variables.

Verify API compatibility instantly

The `get_forgejo_version` and `get_gitea_version` tools pull detailed metadata about your instance. They check the exact release running on your server before attempting API calls. Forks drift over time. By checking both the Forgejo release and the underlying Gitea compatibility layer, your agent knows exactly which endpoints will work.

Setup guide

Set up Forgejo (Gitea Fork) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Forgejo (Gitea Fork) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Forgejo (Gitea Fork) MCP configuration

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

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under forgejo-gitea-fork-mcp.

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 Claude Desktop

Open your `claude_desktop_config.json` file. Add the server details under the `mcpServers` key, save the file, and restart the app.

Yes. Once connected, you can ask the agent to trigger specific CI/CD jobs. It uses the dispatch tool to start the workflow.

It does. You can paste the remote HTTPS URL into the Integrations settings on claude.ai to connect without local configuration.

Local stdio execution handles this perfectly. The agent runs the tools as subprocesses on your machine, using your existing network access.

The server only touches workflow triggers, version metadata, and token generation requests. Your source code never leaves the instance. Authentication happens via your configured endpoint token, keeping your base credentials secure.

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