Skip to content
Vinkius

Forgejo (Gitea Fork) Connector for AI agents.

4 live capabilities

Manage your self-hosted Git instance and trigger CI/CD workflows.

Live agent request Forgejo (Gitea Fork) / Connector

Waiting for input…

AI Agent

Why people use Forgejo (Gitea Fork)

Forgejo (Gitea Fork) for self-hosted Git management

This Connector removes those steps. You stay in your chat or IDE. You tell your agent to make a token for the CI runner, and it is done. You get the credential immediately without ever leaving your workspace.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a conversational interface for your self-hosted Git management.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Hotfix Deployment

    A developer needs to deploy a fix.

  2. Real-world use case 02

    Script Integration

    An engineer needs a token for a local cleanup script.

  3. Real-world use case 03

    Infrastructure Audit

    A sysadmin checks if 5 different servers are on the same Forgejo version using get_forgejo_version.

Complete set · 4capabilities

The complete Forgejo (Gitea Fork) capability set.

These are the exact actions your AI can choose when you ask it to work with Forgejo (Gitea Fork).

Capability set01 / 01

01—04

4 capabilities in this set.

Part of 4 available through Forgejo (Gitea Fork).

  1. 01 Capability

    Create token

    Generates a new personal access token. Use this to quickly get credentials for your scripts without navigating the web UI.

  2. 02 Capability

    Get forgejo version

    Retrieves detailed Forgejo version information. Use this to ensure your instance is up to date and compatible with your capabilities.

  3. 03 Capability

    Get gitea version

    Retrieves the Gitea-compatible version of the Forgejo instance. This helps you verify compatibility when running mixed environments.

  4. 04 Capability

    Dispatch workflow

    Triggers a manual workflow dispatch in Forgejo Actions. This is perfect for starting deployments or builds on demand.

Set up in minutes

One URL. Then ask Forgejo (Gitea Fork) to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Forgejo (Gitea Fork) from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_OGbMMQVsinb0BjKH6qJI5Qwlr4pWGYjZRMU7QWs7/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Forgejo (Gitea Fork), and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Forgejo (Gitea Fork) for the conversation.

Where the request belongs

Work Forgejo can move forward.

Built around the request

This is for the ops engineer tired of clicking through dashboards at 2am or the developer who needs to grab an API token quickly without breaking their flow.

01

DevOps Engineer

Triggers manual builds and audits instance versions across multiple environments during production deployments.

02

Software Developer

Generates personal access tokens for local scripts and automated capabilities without leaving the editor.

03

System Administrator

Monitors the health and version compatibility of self-hosted Git instances to ensure security compliance.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
Gitea logo
01 10 capabilities

Gitea

Manage self-hosted Git via Gitea. list and manage repositories, track issues and pull requests, handle organizations, and audit branches directly from any AI agent.

View Connector
Gitee logo
02 10 capabilities

Gitee

Collaborative code hosting and development platform. manage repositories, issues, and pull requests via AI.

View Connector
Coding.net logo
03 10 capabilities

Coding.net

All-in-one DevOps platform. manage projects, repositories, and issues via AI.

View Connector
Bitbucket logo
04 10 capabilities

Bitbucket

Manage your Git repositories via Bitbucket. list pull requests, commits, and pipelines directly from any AI agent.

View Connector
GitHub logo
05 12 capabilities

GitHub

Manage repositories, pull requests, issues, and CI/CD workflows on the world largest developer collaboration platform.

View Connector
GitLab logo
06 16 capabilities

GitLab

Manage projects, track issues, and oversee CI/CD pipelines via AI agents with GitLab.

View Connector

Bring your own AI

Change the model, client or framework. Keep Forgejo connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Forgejo.

The practical details behind the request, access and result.

Can I use the Forgejo (Gitea Fork) MCP with my self-hosted Git server?

Yes, this Connector is designed specifically for self-hosted Forgejo and Gitea instances. It allows your AI agent to interact with your private Git service directly.

How do I generate API tokens using the Forgejo (Gitea Fork) MCP?

You just ask your AI agent to create a new token for you. It will handle the request to your instance and provide you with the new credential and its scope.

Can the Forgejo (Gitea Fork) MCP trigger my CI/CD builds?

Yes, it can trigger manual workflow dispatches for Forgejo Actions. This means you can start your builds or deployments just by asking your agent to do so.

Does the Forgejo (Gitea Fork) MCP work for both Forgejo and Gitea?

Yes, it supports both. It can retrieve version information for both Forgejo and Gitea-compatible instances.

Is it safe to use the Forgejo (Gitea Fork) MCP for repository management?

Yes, it uses your existing credentials to perform actions. You control the scopes and permissions, so your agent only does what you authorize it to do.

How does the Forgejo (Gitea Fork) MCP help with my DevOps workflow?

It removes the need to constantly switch between your editor and your Git web UI. You can audit versions, manage tokens, and trigger builds without leaving your primary workspace.

How can I check which Forgejo version my instance is running?

You can use the get_forgejo_version capability. It will return the specific version string of your Forgejo instance, which is useful for debugging and feature compatibility checks.

Can I trigger a CI/CD build manually through the AI?

Yes! Use the dispatch_workflow capability by providing the repository owner, name, and the workflow file name. This triggers actions configured with the 'workflow_dispatch' event.

What is required to generate a new API token?

To use the create_token capability, you must have your Forgejo username and password configured in the credentials. This allows the agent to authenticate via BasicAuth and request a new token with your specified scopes.

One connection away

Give your agent a direct line to Forgejo.

Connect Forgejo once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available