Bring Git Repository
to OpenAI Agents SDK
Learn how to connect Forgejo (Gitea Fork) to OpenAI Agents SDK and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 OpenAI Agents SDK?
The OpenAI Agents SDK auto-discovers all 4 tools from Forgejo (Gitea Fork) through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns. chain multiple agents where one queries Forgejo (Gitea Fork), another analyzes results, and a third generates reports, all orchestrated through Vinkius.
- —
Native MCP integration via
MCPServerSse, pass the URL and the SDK auto-discovers all tools with full type safety - —
Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure
- —
Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate
- —
First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output
Forgejo (Gitea Fork) in OpenAI Agents SDK
Forgejo (Gitea Fork) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Forgejo (Gitea Fork) to OpenAI Agents SDK 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 OpenAI Agents SDK
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 OpenAI Agents SDK 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 OpenAI Agents SDK
Every tool call from OpenAI Agents SDK 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 the OpenAI Agents SDK connect to MCP?
Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.
Can I use multiple MCP servers in one agent?
Yes. Pass a list of MCPServerSse instances to the agent constructor. The agent can use tools from all connected servers within a single run.
Does the SDK support streaming responses?
Yes. The SDK supports SSE and Streamable HTTP transports, both of which work natively with Vinkius.
MCPServerStreamableHttp not found
Ensure you have the latest version: pip install --upgrade openai-agents
Agent not calling tools
Make sure your prompt explicitly references the task the tools can help with.
Explore More MCP Servers
View all →
Correios do Brazil
3 toolsCalculate shipping costs, estimate delivery times, and consult address information via the official Correios REST API.
LoadNinja (Real-Browser Load Testing)
10 toolsManage performance tests via LoadNinja — trigger load scenarios, monitor metrics, and audit virtual user (VU) limits.
TfL
12 toolsAccess London transport data via TfL — track tube and bus arrivals, plan journeys, check line status, and find bike points from any AI agent.
Cloze
9 toolsSmart CRM that automatically tracks your interactions and provides AI-powered insights.