An astronaut overseeing a futuristic data hub

Connect Forgejo Gitea Fork to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your Git infrastructure through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Forgejo.

  1. 01

    Create token

    This capability generates a new personal access token for a specific user. Use it to create scoped credentials for scripts or integrations without using the web interface.

  2. 02

    Dispatch workflow

    This capability triggers a manual workflow dispatch within Forgejo Actions. It lets you start builds or deployments directly from your AI chat.

  3. 03

    Get forgejo version

    This capability retrieves detailed version information for your Forgejo instance. It helps you confirm API compatibility for your infrastructure.

  4. 04

    Get gitea version

    This capability checks the Gitea-compatible version of your Forgejo instance. Use it to ensure your automation works with Gitea-based workflows.

Real work

What teams actually run

01

Automated Deployments

Trigger a specific Forgejo Actions workflow immediately after a code change is finished.

02

Rapid Credentialing

Create a new scoped token for a new integration without navigating through the web UI settings.

03

Infrastructure Audits

Verify that all your self-hosted Git instances are running compatible versions before pushing updates.

04

DevOps ChatOps

Manage repository-related tasks using conversational commands instead of manual terminal commands.

Automate a task

Put Forgejo to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Forgejo works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Forgejo to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1043ms average. Fast in production.

Forgejo is checked daily against the live service.

Daily averagePeak 1228ms
Oct 3Today
Fastest day
731ms
Slowest day
1228ms
14-day trend
Improving-23%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Forgejo, so you can see the experience inside your AI.

It does not authenticate your account with Forgejo. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Forgejo Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_OGbMMQVsinb0BjKH6qJI5Qwlr4pWGYjZRMU7QWs7/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Forgejo capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "forgejo-gitea-fork-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_OGbMMQVsinb0BjKH6qJI5Qwlr4pWGYjZRMU7QWs7/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Forgejo in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Forgejo owners hand off.

This MCP is built for technical professionals managing self-hosted Git environments.

  • 01

    DevOps Engineers

    They use the agent to trigger CI/CD pipelines and monitor versions across environments.

  • 02

    Software Developers

    They use the agent to generate API tokens for local scripts without opening a browser.

  • 03

    System Administrators

    They use the agent to audit self-hosted instances and manage access credentials.

FAQ

Questions Forgejo owners ask.

  • 01

    Which Git services does this MCP support?

    This MCP supports Forgejo and Gitea instances.

  • 02

    Can I trigger CI/CD pipelines with this?

    Yes, you can trigger manual workflow dispatches for Forgejo Actions directly through your AI client.

  • 03

    How do I manage API tokens?

    You can use the create_token capability to generate new Personal Access Tokens with specific scopes for any user.

  • 04

    Do I need to host the MCP myself?

    No, Vinkius hosts and manages the MCP for you. You only need to provide your instance URL and credentials.

  • 05

    What AI clients can I use?

    You can use any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 06

    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.

  • 07

    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.

  • 08

    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.

Connect Forgejo to Claude, Cursor, ChatGPT & more