# How to integrate Gitea MCP with Autogen ```json { "title": "How to integrate Gitea MCP with Autogen", "toolkit": "Gitea", "toolkit_slug": "gitea", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/gitea/framework/autogen", "markdown_url": "https://composio.dev/toolkits/gitea/framework/autogen.md", "updated_at": "2026-03-29T06:35:22.769Z" } ``` ## Introduction This guide walks you through connecting Gitea to AutoGen using the Composio tool router. By the end, you'll have a working Gitea agent that can list all open issues in your repository, create a new pull request for dev branch, get commit history for a specific file through natural language commands. This guide will help you understand how to give your AutoGen agent real control over a Gitea account through Composio's Gitea MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Gitea with - [ChatGPT](https://composio.dev/toolkits/gitea/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/gitea/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/gitea/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gitea/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/gitea/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/gitea/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gitea/framework/codex) - [Cursor](https://composio.dev/toolkits/gitea/framework/cursor) - [VS Code](https://composio.dev/toolkits/gitea/framework/vscode) - [OpenCode](https://composio.dev/toolkits/gitea/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/gitea/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gitea/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gitea/framework/cli) - [Google ADK](https://composio.dev/toolkits/gitea/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gitea/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gitea/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gitea/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gitea/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/gitea/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Gitea - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Gitea tools - Run a live chat loop where you ask the agent to perform Gitea operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## What is the Gitea MCP server, and what's possible with it? The Gitea MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Gitea account. It provides structured and secure access so your agent can perform Gitea operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `GITEA_ACTIVITYPUB_PERSON` | Get ActivityPub Person Actor | Tool to retrieve the ActivityPub Person actor for a Gitea user. Use when you need to fetch a user's ActivityPub representation for federation purposes or to get ActivityStreams-formatted user data. | | `GITEA_GET_GENERAL_API_SETTINGS` | Get General API Settings | Tool to retrieve the Gitea instance's global API settings including pagination limits and response size constraints. Use when you need to understand API rate limits or configuration parameters. | | `GITEA_GET_GENERAL_ATTACHMENT_SETTINGS` | Get General Attachment Settings | Tool to retrieve the Gitea instance's global settings for file attachments including enabled status, allowed file types, size limits, and file count limits. Use when you need to understand the attachment configuration of the instance. | | `GITEA_GET_GENERAL_REPOSITORY_SETTINGS` | Get General Repository Settings | Tool to retrieve the Gitea instance's global settings for repositories including feature flags for mirroring, HTTP Git, migrations, stars, time tracking, and LFS. Use when you need to understand which repository features are enabled or disabled at the instance level. | | `GITEA_GET_GENERAL_UI_SETTINGS` | Get General UI Settings | Tool to retrieve the Gitea instance's global settings for UI including default theme, allowed reactions, and custom emojis. Use when you need to understand the UI configuration of the instance. | | `GITEA_GET_GITIGNORE_TEMPLATE_INFO` | Get Gitignore Template Info | Tool to retrieve information about a specific gitignore template. Use when you need the content of a gitignore template for repository creation or configuration. | | `GITEA_GET_LABEL_TEMPLATE_INFO` | Get Label Template Info | Tool to retrieve all labels from a specific label template. Use when you need to view the predefined label set for repository configuration. | | `GITEA_GET_LICENSE_TEMPLATE_INFO` | Get License Template Info | Tool to retrieve information about a specific license template. Use when you need the content and details of a license template for repository creation or configuration. | | `GITEA_GET_NODE_INFO` | Get Node Info | Tool to retrieve the nodeinfo of the Gitea application. Use when you need standardized metadata about the Gitea server following the NodeInfo specification. | | `GITEA_GET_SIGNING_KEY` | Get Signing Key | Tool to retrieve the default GPG signing key used by Gitea to sign commits. Use when you need to verify commits signed by the Gitea instance or import the public key to trust Gitea-generated commits. | | `GITEA_GET_VERSION` | Get Version | Tool to retrieve the version of the Gitea application. Use when you need to check the Gitea server version. | | `GITEA_LIST_GITIGNORE_TEMPLATES` | List Gitignore Templates | Tool to retrieve all available gitignore templates. Use when creating a repository to select an appropriate .gitignore template. | | `GITEA_LIST_LABEL_TEMPLATES` | List Label Templates | Tool to retrieve all available label templates. Use when you need to discover which predefined label sets are available for repositories. | | `GITEA_LIST_LICENSE_TEMPLATES` | List License Templates | Tool to retrieve all available license templates. Use when creating a repository to select an appropriate license template. | | `GITEA_GET_ALL_ORGANIZATIONS` | Get All Organizations | Tool to retrieve a paginated list of all organizations in the Gitea instance. Use when you need to list all organizations or browse organizations with pagination support. | | `GITEA_LIST_ORGANIZATION_ACTIONS_SECRETS` | List Organization Actions Secrets | Tool to list all action secrets for an organization. Use when you need to retrieve the list of secrets configured at the organization level. Note that secret values are never returned through the API for security purposes. | | `GITEA_RENDER_MARKDOWN` | Render Markdown | Tool to render a markdown document as HTML with configurable rendering modes and context. Use when you need to convert markdown to HTML with specific rendering contexts like comments, wiki pages, or files. | | `GITEA_RENDER_MARKDOWN_RAW` | Render Markdown Raw | Tool to render raw markdown text as HTML. Use when you need to convert markdown content to HTML format for display or processing. | | `GITEA_RENDER_MARKUP` | Render Markup | Tool to render a markup document as HTML with support for multiple markup formats. Use when you need to convert markup content (Markdown, AsciiDoc, etc.) to HTML with specific rendering contexts like comments, wiki pages, or files. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Gitea MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Gitea. Instead of manually wiring Gitea APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Gitea account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Gitea via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Gitea connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Gitea tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Gitea session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["gitea"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Gitea tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Gitea assistant agent with MCP tools agent = AssistantAgent( name="gitea_assistant", description="An AI assistant that helps with Gitea operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Gitea tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Gitea related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Gitea session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["gitea"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Gitea assistant agent with MCP tools agent = AssistantAgent( name="gitea_assistant", description="An AI assistant that helps with Gitea operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Gitea related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Gitea through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Gitea, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build Gitea MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/gitea/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/gitea/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/gitea/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/gitea/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/gitea/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/gitea/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/gitea/framework/codex) - [Cursor](https://composio.dev/toolkits/gitea/framework/cursor) - [VS Code](https://composio.dev/toolkits/gitea/framework/vscode) - [OpenCode](https://composio.dev/toolkits/gitea/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/gitea/framework/openclaw) - [Hermes](https://composio.dev/toolkits/gitea/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/gitea/framework/cli) - [Google ADK](https://composio.dev/toolkits/gitea/framework/google-adk) - [LangChain](https://composio.dev/toolkits/gitea/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/gitea/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/gitea/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/gitea/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/gitea/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Gitea MCP? With a standalone Gitea MCP server, the agents and LLMs can only access a fixed set of Gitea tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Gitea and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Autogen? Yes, you can. Autogen fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Gitea tools. ### Can I manage the permissions and scopes for Gitea while using Tool Router? Yes, absolutely. You can configure which Gitea scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Gitea data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)