How to Use the Forgejo (Gitea Fork) MCP in Cursor
Keep your hands on the keyboard. Connect your Forgejo (Gitea Fork) instance to Cursor and trigger deployments directly from your code editor.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Forgejo (Gitea Fork) MCP to Cursor
Create your Vinkius account to connect Forgejo (Gitea Fork) to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Native MCP Server instance validation
The `get_forgejo_version` and `get_gitea_version` tools fetch the exact release running on your git host. Cursor reads this data to write API calls that match your specific deployment. You don't have to guess if a new endpoint is supported. The agent checks the version first, then writes the integration code based on actual server capabilities.
Provision API keys mid-code
The `create_token` tool generates new personal access tokens while you write integration scripts. Cursor provisions a real credential instead of leaving a placeholder in your code. Switching windows to generate a token breaks focus. Now, you tell the editor you need access, it creates the key, and injects it straight into your current file.
Fire off builds from the editor
The `dispatch_workflow` tool kicks off Forgejo Actions directly from your workspace. After you commit a change, you can tell the agent to run the test suite. It completely changes how you test remote pipelines. Let's face it, clicking through a web UI is slow. You write the workflow file, commit it, and trigger a run in seconds without ever opening a browser tab.
Set up Forgejo (Gitea Fork) MCP in Cursor
Prerequisites
- Cursor installed (macOS, Windows, or Linux)
- Active Vinkius subscription with a valid endpoint token
- 1
Open MCP Settings
Go to Cursor Settings → MCP or open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) and search for "MCP: Add Server". - 2
Add the Forgejo (Gitea Fork) MCP
Cursor will create or open
.cursor/mcp.jsonin your project root. Paste the JSON snippet on the right. Replace[YOUR_TOKEN_HERE]with your endpoint token from cloud.vinkius.com. - 3
Enable Agent mode
Open Composer (
Cmd+I/Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode. - 4
Verify the connection
Ask Cursor something like "List my recent Forgejo (Gitea Fork) transactions." If the MCP tools are loaded correctly, Cursor will call the Forgejo (Gitea Fork) tools automatically. You can also check Settings → MCP for a green status indicator.
{
"mcpServers": {
"forgejo-gitea-fork-mcp": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
} 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.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about Forgejo (Gitea Fork) MCP in Cursor
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Forgejo (Gitea Fork) MCP today
We host it, we monitor it, we maintain it. You just paste one token.