4,000+ servers built on vurb.ts
Vinkius
LangChainFramework
Forgejo (Gitea Fork) MCP Server

Bring Git Repository
to LangChain

Learn how to connect Forgejo (Gitea Fork) to LangChain and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create TokenDispatch WorkflowGet Forgejo VersionGet Gitea Version

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Forgejo (Gitea Fork)

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

  1. Subscribe to this server
  2. Enter your Forgejo Instance URL and credentials (Token or Username/Password)
  3. 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)

create_token

Generates a new personal access token. Generate a new API token for a user

dispatch_workflow

Trigger a manual workflow dispatch in Forgejo Actions

get_forgejo_version

Get detailed Forgejo version information

get_gitea_version

Get the Gitea-compatible version of the Forgejo instance

Why LangChain?

LangChain's ecosystem of 500+ components combines seamlessly with Forgejo (Gitea Fork) through native MCP adapters. Connect 4 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

  • The largest ecosystem of integrations, chains, and agents. combine Forgejo (Gitea Fork) MCP tools with 500+ LangChain components

  • Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

  • LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

  • Memory and conversation persistence let agents maintain context across Forgejo (Gitea Fork) queries for multi-turn workflows

See it in action

Forgejo (Gitea Fork) in LangChain

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Forgejo (Gitea Fork) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Forgejo (Gitea Fork) to LangChain 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Forgejo (Gitea Fork) in LangChain

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 LangChain 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.

Forgejo (Gitea Fork)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Forgejo (Gitea Fork) for LangChain

Every tool call from LangChain to the Forgejo (Gitea Fork) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.

05

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.

06

Can I trace MCP tool calls in LangSmith?

Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.

07

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

Explore More MCP Servers

View all →