SpecForge
Allows autonomous code fixing from GitHub issues: reads repository, plans fix, writes code, tests, and opens pull requests directly on GitHub.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SpecForgeFix the bug in https://github.com/myorg/myrepo/issues/42"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SpecForge
Turn GitHub issues into merged pull requests — autonomously.
SpecForge is a Model Context Protocol (MCP) server that connects an LLM client (like Claude Desktop) to a fully autonomous code-fixing pipeline. Point it at a GitHub issue, and it reads the repo, plans a fix, writes the code, tests it, and opens a pull request — without a human touching the keyboard in between.
Built for the CyOps Arena x MiniMax M3 Hackathon 2025.
How It Works
SpecForge orchestrates four stages, each handled by a specialized agent:
Stage | Agent | What Happens |
1. Recon | Recon Agent | Reads repo structure, detects language, package manager, and test runner |
2. Plan | Planning Agent | Generates a file-level implementation plan from the issue description |
3. Implement | MiniMax M3 | Writes the actual code changes |
4. Review | Review Agent | Runs tests, self-critiques, and loops until the suite passes |
5. Ship | GitHub Agent | Creates a branch, commits changes, and opens a pull request |
You give it an issue URL. It gives you back a PR.
Related MCP server: Gravitas-Core-MCP
Prerequisites
Requirement | Notes |
Node.js | v18 or higher |
npm | v9 or higher |
CyOps account | Free signup at ai.cysic.xyz |
GitHub Personal Access Token | Needs |
Installation
1. Install dependencies
cd mcp-server
npm install
npm run build2. Configure environment variables
cp .env.example .envEdit .env with your credentials:
# GitHub — token needs repo, pull_requests, and contents (read + write) scopes
GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
# CyOps Gateway URL (from your ai.cysic.xyz workspace)
CYOPS_GATEWAY_URL=https://your-instance.cysic.xyz
# CyOps API key (Settings → API Keys, inside your workspace)
CYOPS_API_KEY=cyops_xxxxxxxxxxxxxxxxxxxx3. Set MiniMax M3 as your model in CyOps
Open your CyOps workspace and click Open Gateway
Go to Settings → LLM Proxy
Set each agent's model to MiniMax M3
This unlocks the hackathon's 80% discount on token pricing.
4. Connect to Claude Desktop
Open your Claude Desktop config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add SpecForge as an MCP server:
{
"mcpServers": {
"specforge": {
"command": "node",
"args": ["/absolute/path/to/mcp-server/dist/index.js"]
}
}
}Restart Claude Desktop. SpecForge should now appear in your available tools.
Usage
In Claude Desktop, just describe what you want fixed:
Use specforge to fix https://github.com/org/repo/issues/42SpecForge runs the full pipeline and returns a pull request URL when finished. No further input required unless you want to check progress mid-run.
Available Tools
specforge_run
Kicks off the full pipeline for a given issue.
{
issue_url: string; // Required — full GitHub issue URL
strategy_profile?: string; // Optional — CyOps strategy (default: "Default RLCR (Claude → MiniMax M3)")
max_wait_minutes?: number; // Optional — timeout in minutes (default: 10)
}specforge_status
Checks the status of an in-progress run.
{
run_id: string; // CyOps run ID, returned from specforge_run
project_id: string; // CyOps project ID, returned from specforge_run
}Architecture
specforge_run (MCP tool)
│
├── parseIssueUrl() → Parse the GitHub issue URL
├── fetchIssue() → Read issue body + comments
│
├── runRecon() → Recon Agent
│ ├── fetchRepoContext()
│ ├── readFile() × N → package.json, tsconfig, etc.
│ └── detect test runner, package manager
│
├── createProject() → CyOps: create new project
├── generatePlan() → CyOps: generate plan from requirement
├── startRun() → CyOps: begin Implement → Review loop
├── pollRun() → CyOps: wait for completion
│
├── getArtifacts() → List changed files
├── readWorkspaceFile() × N → Read each changed file
├── createBranch() → GitHub: create new branch
├── commitFileToGitHub() × N → GitHub: push each changed file
└── openPullRequest() → GitHub: open pull requestProject Structure
mcp-server/
├── src/
│ ├── index.ts # MCP server entry point + tool handlers
│ ├── github.ts # GitHub API client
│ ├── cyops.ts # CyOps Gateway API client
│ └── agents/
│ ├── recon.ts # Recon Agent — repo understanding
│ └── orchestrator.ts # Main pipeline coordinator
├── package.json
├── tsconfig.json
└── README.mdHackathon
CyOps Arena x MiniMax M3 — June 2025
This server cannot be deployed
Maintenance
Related MCP Connectors
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
AI code review for GitHub PRs with an MCP autofix loop for Claude Code and Cursor
MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that diagnoses GitHub Actions workflow failures and automatically creates repair pull requests using LLM-generated unified diffs. It includes a governance layer to orchestrate autonomous fixes or human-reviewed repairs based on risk assessment thresholds.-
- AlicenseBqualityCmaintenanceProduction-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.211MIT
- AlicenseAqualityCmaintenanceAn MCP server that enables autonomous code development by pulling GitHub issues, fixing them in a sandboxed environment, running tests, opening PRs, and promoting to production upon human approval.3AGPL 3.0
- AlicenseAqualityAmaintenanceAn autonomous, extensible LLM build orchestrator. Give it a repo and a goal; it decomposes the goal into tasks, edits code, and gates every change on build/tests/lint, reverting regressions. Polygot, cost-aware model selection, pluggable via entry points. Ships as an MCP server so any client can drive it in plain English.153AGPL 3.0