How to Use the Gitea MCP in Cursor

Q: How do I configure Cursor to talk to my self-hosted Gitea?

Add the Gitea MCP server to your project-scoped .cursor/mcp.json file. Once configured, Cursor can immediately execute tools like listrepos to assist your development flow.

Write code in Cursor with real-time context from your Gitea repositories, issues, and branches.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gitea MCP to Cursor

Create your Vinkius account to connect Gitea 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.

GDPR Free for Subscribers

Setup Gitea with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Gitea MCP Server tools inside Cursor

Stop writing code in Cursor based on outdated Gitea API schemas or stale local clones. This Gitea MCP server allows the Cursor Agent to run `get_repo` and `list_repos` to pull actual repository structures directly into your active coding session. Your Cursor editor context reads real-time Gitea metadata rather than relying on static mock data. The Cursor agent uses `get_me` to verify your Gitea permissions before pulling down repository configurations.

Reference Gitea issues while coding in Cursor

Fix Gitea bugs faster by letting the Cursor Agent read the exact Gitea issue description you are working on. Cursor calls `list_issues` to find your assigned Gitea tickets, then runs `get_issue` to extract requirements directly into your sidebar. You don't have to copy-paste error logs from Gitea into Cursor anymore. Gathering Gitea context becomes the Cursor editor's job, letting you focus entirely on writing the fix.

Track Gitea branches and PRs inside Cursor

Keep your Cursor workspace aligned with your remote self-hosted Gitea server without running manual git terminal commands. Running `list_pulls` and `list_branches` allows Cursor to check if your active file conflicts with open Gitea pull requests. Understanding Gitea team velocity becomes part of your Cursor Agent editing flow. By querying `list_org_repos` and `list_orgs`, the Cursor editor ensures you are pushing code to the correct Gitea organizational upstream.

Setup guide

Set up Gitea 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 Gitea MCP

Cursor will create or open .cursor/mcp.json in 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 Gitea transactions." If the MCP tools are loaded correctly, Cursor will call the Gitea tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "gitea-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gitea. 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.

Connect Gitea now

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 Gitea MCP in Cursor

Add the Gitea MCP server to your project-scoped `.cursor/mcp.json` file. Once configured, Cursor can immediately execute tools like `list_repos` to assist your development flow.

While the agent can't write directly to your git database, it uses `list_pulls` and `list_branches` to analyze code differences. This lets Cursor suggest precise edits in your editor to prevent merge conflicts on Gitea.

Yes, Composer mode fully supports these tools. You can ask the editor to write a feature and it will use `get_issue` to read the specifications directly from your Gitea instance.

The editor coordinates tool execution to prevent overwhelming your Gitea instance. It spaces out calls to heavy endpoints like `list_org_repos`, keeping your self-hosted Gitea server stable.

Your Gitea access token is stored securely within Cursor's local configuration or your environment variables. The MCP server processes your Gitea repository metadata and branch structures in a secure V8 sandbox, ensuring your authentication credentials never leak.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript