Compatible with every major AI agent and IDE
What is the Forgejo (Gitea Fork) MCP Server?
Connect your Forgejo or Gitea instance to any AI agent to streamline your DevOps and repository management workflows through natural conversation.
What you can do
- Version Auditing — Retrieve detailed Forgejo and Gitea-compatible version information to ensure API compatibility across your infrastructure.
- Token Management — Generate new Personal Access Tokens (PATs) with specific scopes (read/write) using your BasicAuth credentials.
- CI/CD Automation — Trigger manual workflow dispatches for Forgejo Actions directly from the chat to start builds or deployments.
- Instance Inspection — Verify the health and configuration of your self-hosted Git service without leaving your development environment.
How it works
- Subscribe to this server
- Enter your Forgejo Instance URL and credentials (Token or Username/Password)
- Start managing your repositories and actions from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — automate the triggering of CI/CD pipelines and monitor instance versions across multiple environments.
- Software Developers — generate API tokens for local scripts or integrations without navigating the web UI.
- System Administrators — quickly audit self-hosted Git instances and manage access credentials via AI assistance.
Built-in capabilities (4)
Generates a new personal access token. Generate a new API token for a user
Trigger a manual workflow dispatch in Forgejo Actions
Get detailed Forgejo version information
Get the Gitea-compatible version of the Forgejo instance
Why Claude Desktop?
Claude Desktop is the definitive way to connect Forgejo (Gitea Fork) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 4 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Forgejo (Gitea Fork) in Claude Desktop
Forgejo (Gitea Fork) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Forgejo (Gitea Fork) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Forgejo (Gitea Fork) in Claude Desktop
The Forgejo (Gitea Fork) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Forgejo (Gitea Fork) for Claude Desktop
Every tool call from Claude Desktop to the Forgejo (Gitea Fork) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check which Forgejo version my instance is running?
You can use the get_forgejo_version tool. 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 tool 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 tool, 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Weights & Biases
6 toolsTrack experiments, monitor ML runs, and manage artifacts on WandB — the developer platform for AI.

Withings
10 toolsAccess comprehensive health and fitness data — track weight, blood pressure, sleep cycles, steps, workouts, and heart rate directly from Withings devices.

Mailgun (Transactional Email & Domains)
10 toolsManage email infrastructure via Mailgun — send transactional emails, monitor domain health, and audit delivery logs.

Moodle
10 toolsManage your Learning Management System via Moodle — track courses, users, assignments, and grades directly from your AI agent.
