Vinkius

Forgejo (Gitea Fork) MCP. Manage CI/CD and Repo Access in Chat

Forgejo (Gitea Fork) MCP connects your self-hosted Git instances to any AI agent. It lets you manage repository access, check version compatibility across multiple environments, and trigger CI/CD workflows—all from a single conversation. Need an API token or running a deployment test? This is where you do it.

Forgejo (Gitea Fork) MCP is compatible with Claude Claude
Forgejo (Gitea Fork) MCP is compatible with ChatGPT ChatGPT
Forgejo (Gitea Fork) MCP is compatible with Cursor Cursor
Forgejo (Gitea Fork) MCP is compatible with Gemini Gemini
Forgejo (Gitea Fork) MCP is compatible with Windsurf Windsurf
Forgejo (Gitea Fork) MCP is compatible with VS Code VS Code
Forgejo (Gitea Fork) MCP is compatible with JetBrains JetBrains
Forgejo (Gitea Fork) MCP is compatible with Vercel Vercel
See Vinkius in Action

Give Claude and any AI agent real-world access

Audit self-hosted version compatibility

You can retrieve detailed version numbers for both Forgejo and Gitea, confirming API compatibility across your infrastructure.

Generate new access tokens

The agent generates Personal Access Tokens (PATs) using your basic credentials, allowing you to grant specific read or write scopes instantly.

Trigger CI/CD pipelines manually

You can execute manual workflow dispatches for Forgejo Actions directly from the chat interface to start builds or deployments.

Waiting for input…

AI Agent
Forgejo (Gitea Fork)

What AI agents can do with Forgejo (Gitea Fork) MCP: 4 Tools

These tools allow you to audit versions, generate credentials, and automate deployments across your self-hosted Git instances.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Forgejo (Gitea Fork) MCP

Create Token

Generates a new personal access token for a specified user with defined permissions.

Dispatch Workflow

Triggers a manual workflow run within Forgejo Actions.

Get Forgejo Version

Retrieves detailed version information for the connected Forgejo instance.

Get Gitea Version

Gets the Gitea-compatible version data from your self-hosted Git service.

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Forgejo (Gitea Fork) MCP is compatible with Claude

Claude AI

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) integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on each call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Forgejo (Gitea Fork), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,200+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Connections are secured and governed automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog weekly
Forgejo (Gitea Fork) MCP server cover

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.

VINKIUS CLOUD

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on each call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

The headache of managing self-hosted Git infrastructure

Right now, if you need to audit your system, you're bouncing between tabs. You check Forgejo for its version, then switch over to another dashboard to see what the Gitea compatibility looks like. If you also need a new API key for a testing script, that means logging in again and navigating through user settings just to generate a PAT.

With this MCP, your agent handles it all. You simply ask: 'What are my versions, and can I get a token for read access?' The system runs the checks and generates the credential without you touching a single dashboard. It keeps your entire process contained in the chat.

Generate API tokens with `create_token`

Previously, generating an access token meant logging into the web UI, finding the 'API' section, ensuring you selected the correct scope (read or write), and then copying a long string of characters. This process is slow and requires manual verification.

Now, you just ask your agent to use `create_token` with specific scopes and user details. The token appears immediately in the chat, ready for copy-pasting. It's faster, safer, and cuts out three clicks.

What Forgejo (Gitea Fork) MCP does for your AI

Connect your Forgejo or Gitea self-hosted Git instance to any AI agent to handle complex DevOps tasks naturally. Instead of logging into multiple dashboards, checking version numbers across different tabs, and manually generating access tokens, you just ask your agent. You can check detailed version compatibility between Forgejo and Gitea APIs, generate new Personal Access Tokens with specific read/write scopes, or kick off a full CI/CD build by dispatching workflows directly from the chat.

The Vinkius catalog makes this connection simple; once connected to any compatible client, you get access to all these Git management functions. It’s about keeping your entire development process in one conversation.

Built · Hosted · Managed by Vinkius Forgejo (Gitea Fork) MCP - DevOps Automation
Server ID 019e389a-9bd8-737b-9625-bcc0c43a7e01
Vinkius Inspector
Compliance Grade F
Score 43.65/100
Vinkius Inspector Badge — Score 43.65/100

Frequently asked questions about Forgejo (Gitea Fork) MCP

How do I check the version compatibility using Forgejo (Gitea Fork) MCP? +

You need to use get_forgejo_version for your Forgejo data and then call get_gitea_version to get the corresponding Gitea-compatible API data. This tells you if they talk to each other.

Can I trigger a workflow manually with Forgejo (Gitea Fork) MCP? +

Yes, you use dispatch_workflow. You just tell the agent which YAML file and repository needs the build, and it sends the manual dispatch command for you.

Does create_token require specific permissions? +

Yes, the AI agent uses your basic credentials to generate tokens. Make sure the account connected has the necessary admin rights to issue new Personal Access Tokens (PATs).

Is this MCP only for Forgejo instances? +

No, it's designed for both Forgejo and Gitea-compatible self-hosted Git services. You'll need to provide the correct instance URL when setting up your connection.

What if my workflow fails? Can I check the version using Forgejo (Gitea Fork) MCP? +

While this MCP doesn't monitor live build logs, it can help diagnose potential causes by running get_forgejo_version or get_gitea_version. Version mismatch is often the root cause.