In-depth architectural comparison of the Forgejo MCP and Oss Autopilot MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Forgejo MCP
Version Control · Local stdio
Quality: 35/100 (Fair) | Auth: API Key required
Oss Autopilot
Version Control · Local stdio
Quality: 60/100 (Good) | Auth: other
Verdict Summary: Choose Forgejo MCP if you need specialized Version Control tools running via a local process. Choose Oss Autopilot if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Forgejo MCP when:
You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: FORGEJOMCP_SERVER, FORGEJOMCP_TOKEN.
Primary tools included: Issue creation, editing, commenting, and dependency management, Label and milestone CRUD operations, Repository search and listing.
An MCP server for managing your repositories on Forgejo/Gitea server.
Open source contribution manager with PR tracking across repos, issue discovery, CI failure diagnosis, and maintainer response drafting. Available as CLI, MCP server, and Claude Code plugin.
Forgejo MCP is categorized under Version Control and uses a local stdio subprocess. In contrast, Oss Autopilot belongs to Version Control using local stdio subprocess. Select Forgejo MCP when you need capabilities focused on version control and Oss Autopilot when you require tools for version control.