How to Use the Forgejo (Gitea Fork) MCP in LlamaIndex

Q: How do I index Forgejo (Gitea Fork) data with LlamaIndex?

Install llama-index-tools-mcp. Initialize BasicMCPClient and pass the resulting tools to your FunctionAgent for execution.

Q: How do I restrict which tools the agent can use?

Use the allowedtools filter when setting up your McpToolSpec. You can block token creation while allowing version checks.

Index your CI/CD pipelines and versions with Forgejo (Gitea Fork) and LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Forgejo (Gitea Fork) MCP to LlamaIndex

Create your Vinkius account to connect Forgejo (Gitea Fork) to LlamaIndex 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 Forgejo (Gitea Fork) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Forgejo Version Metadata

Extracting infrastructure details directly into your LlamaIndex vector store requires the `get_forgejo_version` and `get_gitea_version` tools. Your RAG application queries the live API to check compatibility before answering deployment questions. Stale documentation causes broken builds. This MCP Server pulls the actual running version of your git instance. You ask your agent if a specific feature is supported, and it answers based on live server data, not outdated text files.

Trigger Workflows from RAG Queries

The `dispatch_workflow` tool fires off Forgejo Actions based on semantic search results. You ask LlamaIndex to deploy the latest stable release, and the FunctionAgent maps that intent to the correct pipeline trigger. You connect natural language directly to your CI/CD infrastructure. The agent reads the runbook from your knowledge base, identifies the correct workflow ID, and executes the deployment sequence without manual intervention.

Provision Tokens via LlamaIndex Agents

When your LlamaIndex application needs to authenticate external scripts, the `create_token` tool issues personal access tokens. The agent generates the key, passes it to the target system, and logs the action. This keeps your operations moving. Instead of waiting for an admin to generate a key, the agent handles it securely based on the rules you defined in its system prompt.

Setup guide

Set up Forgejo (Gitea Fork) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Forgejo (Gitea Fork) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Forgejo (Gitea Fork) tools.",
)
response = await agent.run("List recent Forgejo (Gitea Fork) data")

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

Connect Forgejo (Gitea Fork) 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 Forgejo (Gitea Fork) MCP in LlamaIndex

Install `llama-index-tools-mcp`. Initialize `BasicMCPClient` and pass the resulting tools to your `FunctionAgent` for execution.

The current MCP tools support triggering new workflows and checking versions. You index the resulting artifact logs separately to search historical run data.

Use the `allowed_tools` filter when setting up your `McpToolSpec`. You can block token creation while allowing version checks.

Yes. The router can direct CI/CD-related queries specifically to the agent holding these MCP tools.

The connection relies on ephemeral, zero-trust execution. Token generation requests pass through an encrypted tunnel, and the server discards the payload the millisecond the request finishes.

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