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.
Give Claude and any AI agent real-world access
You can retrieve detailed version numbers for both Forgejo and Gitea, confirming API compatibility across your infrastructure.
The agent generates Personal Access Tokens (PATs) using your basic credentials, allowing you to grant specific read or write scopes instantly.
You can execute manual workflow dispatches for Forgejo Actions directly from the chat interface to start builds or deployments.
Ask an AI about this
Waiting for input…
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) MCPCreate 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.
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
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
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
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.
019e389a-9bd8-737b-9625-bcc0c43a7e01 How to set up Forgejo (Gitea Fork) MCP
The bottom line is you manage complex repository and deployment tasks without ever leaving your chat interface.
Subscribe to this MCP, providing your specific Forgejo Instance URL and necessary credentials (Token or Username/Password).
Your AI agent connects to the instance via the Vinkius framework, authenticating access to your repositories.
You simply ask your agent to perform a task—like checking versions or triggering a workflow—and it handles the rest.
Who uses Forgejo (Gitea Fork) MCP
DevOps Engineers who hate context switching, Software Developers needing quick API credentials, or System Administrators responsible for auditing multiple Git instances. You're the person who gets tired of clicking through five different web portals just to check if a build passed.
Automatically triggering CI/CD pipelines and monitoring instance versions across dev, staging, and production environments.
Generating API tokens for local scripts or integrating third-party tools without having to navigate the web UI’s user settings page.
Quickly auditing self-hosted Git instances and managing access credentials via natural conversation, keeping records clean.
Benefits of connecting Forgejo (Gitea Fork) MCP
Version checks are instant. Instead of manually navigating the UI to check compatibility, you ask your agent to run get_forgejo_version and get_gitea_version for a full audit.
Token management is fast. Need an API key for a local script? Use create_token to generate a new Personal Access Token instantly without leaving the chat window.
CI/CD automation happens on command. You can trigger builds or deployments by calling dispatch_workflow, eliminating the need to click through multiple pipeline dashboards.
Reduce context switching. All your core DevOps tasks—from checking versions to running pipelines—are centralized and managed via a single conversation with your agent.
Deep visibility into self-hosted systems. You can verify instance health and configuration using this MCP, giving you immediate answers without having to log in repeatedly.
Forgejo (Gitea Fork) MCP use cases
Audit versioning across environments
A sysadmin needs to know if their staging environment's Forgejo instance is compatible with the new Gitea API standard. They ask the agent, and it executes get_forgejo_version and get_gitea_version, immediately confirming compatibility before they write a single line of code.
On-demand credential generation
A developer is building a script that needs read access to the main repo but shouldn't have write permissions. Instead of asking an admin, they use create_token to generate a dedicated PAT with only the 'read:repository' scope.
Testing deployment readiness
A team lead needs to ensure the latest code pushes correctly by triggering a full build. They instruct their agent to run dispatch_workflow for the release.yaml, confirming the pipeline starts without any manual clicks.
Troubleshooting environment issues
A junior developer reports that one service is failing mysteriously. The senior engineer asks the agent to verify the overall health by running version checks, quickly diagnosing if the problem is due to API incompatibility between the two Git systems.
Forgejo (Gitea Fork) MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Manually checking versions
Jumping between Forgejo's settings page and Gitea's documentation just to compare version numbers. This process is slow, error-prone, and requires keeping track of multiple tabs.
Instead, ask your agent to run get_forgejo_version and then follow up with a request for the Gitea compatibility data using get_gitea_version. It gives you both numbers in one response.
Using old credentials
Trying to manually update an API key by copying it from notes, only to find out the scope was wrong or the token expired. This wastes time and requires a second admin request.
Use create_token directly in the chat. You tell your agent exactly which scopes (read/write) you need for the new credential set.
Forgetting to start the pipeline
Assuming that a merge into main automatically starts the necessary build, only for the deployment to fail because no one remembered to manually kick off the workflow.
Don't assume it. Use dispatch_workflow and specify the exact YAML file (e.g., 'deploy.yaml') to guarantee the required CI/CD job runs.
When to use Forgejo (Gitea Fork) MCP
Use this MCP if your daily work involves coordinating multiple, distinct actions across a self-hosted Git stack—like generating tokens AND checking versions AND running builds. You need an AI agent to manage these operational tasks in sequence within one chat session.
Don't use this if you only need basic, single-purpose interaction (e.g., just viewing commit history or pulling code). For simple reading/writing of repository content, stick to your standard Git CLI tools. This MCP is for the meta-tasks: the governance, auditing, and automation around the repo itself.
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.