RepoPilot
Provides tools for managing GitHub issues, pull requests, checks, and controlled merges, with full audit trail and approval workflows.
Enables monitoring failed GitHub Actions CI runs and driving them through reproduction, fix, verification, and pull request creation.
Click on "Install 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., "@RepoPilotInvestigate the failing CI build and open a verified PR"
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.
RepoPilot 建立在 AgentTeams
v1.2.2之上,面向 GOAI「新智基座 · Agent Infra」赛道设计。默认策略为pull_request_only:Agent 可以创建分支、提交和 Pull Request,但不能自动合并、 删除分支、修改权限或密钥。
维护闭环
GitHub Issue / Failed CI
│
▼
Repo Lead 分诊与拆解
│
▼
Locator 根因定位 ──► Fixer 最小修复 ──► Verifier 独立验证
│
人工审批 ◄── 高风险门禁 ◄─────┤
│
▼
Archivist 沉淀 Runbook每个关键阶段都会把决策、工具调用、Git 引用、CI 结果和审批事件写入 PostgreSQL 追加式 SHA-256 证据链,并通过 OpenTelemetry Trace 与证据控制台支持回放。
Related MCP server: gts-repo-guardian
为什么是 RepoPilot
AgentTeam
Agent Identity 完整定义位于
deploy/agentteams/repopilot-team.yaml,
Skill 契约位于 skills/。
核心能力
系统架构
flowchart LR
GH[GitHub Issue / Failed CI] --> CP[RepoPilot Control Plane]
CP --> DB[(PostgreSQL + pgvector)]
CP --> MX[Matrix Admin → Manager DM]
MX --> M[AgentTeams Manager]
M --> TL[Repo Lead]
TL --> L[Locator]
TL --> F[Fixer]
TL --> V[Verifier]
TL --> A[Archivist]
L & F & V & A --> MCP[RepoPilot MCP via Higress]
MCP --> GHAPI[GitHub REST API]
MCP --> DB
DB --> UI[Evidence Console]
CP --> OTEL[OTLP / AgentLoop / LoongSuite]更多设计细节见 docs/architecture.md。
工程结构
RepoPilot/
├── apps/
│ ├── control-plane/ # Fastify REST / Webhook / MCP / 审批 / 证据账本
│ └── console/ # 飞行记录器风格 React 证据控制台
├── packages/contracts/ # Zod Schema、共享类型和显式状态机
├── deploy/agentteams/ # AgentTeams v1.2.2 Worker / Team 清单
├── skills/ # 5 个可复用 RepoPilot Skills
├── competition/ # 初赛简介、评审映射和提交清单
├── docs/ # 架构、安全、部署和 Demo 文档
├── API.md # REST / Webhook / MCP 出入参
├── Method.md # 外部 SDK、HTTP Method 与调用契约
└── docker-compose.yml # PostgreSQL 16 + pgvector快速开始
环境要求
Node.js
20+pnpm
9+Docker Desktop / Docker Engine
模型凭证不是构建、测试或本地控制面运行的前置条件。
git clone https://github.com/wellkilo/RepoPilot.git
cd RepoPilot
cp .env.example .env
docker compose up -d postgres
pnpm install --registry=https://registry.npmjs.org
pnpm build
pnpm --filter @repopilot/control-plane start访问控制台:
http://127.0.0.1:3000也可以使用一键初始化:
./init.sh创建首个 Run
curl -X POST http://127.0.0.1:3000/api/v1/runs \
-H 'Content-Type: application/json' \
-d '{
"source": {
"type": "github_issue",
"repository": "wellkilo/repopilot-testbed",
"issueNumber": 1
},
"executionPolicy": "pull_request_only"
}'需要读取 GitHub Issue 时,在本机 .env 配置 GITHUB_TOKEN。如果没有配置
AgentTeams Matrix,Run 会停在 awaiting_dispatch,不会用 Mock Agent 伪造执行结果。
AgentTeams 真实协作
真实五 Agent 推理需要一个 OpenAI 兼容模型端点,可以使用:
阿里云百炼等托管服务;
其他 OpenAI 兼容 API;
本地 Ollama 等兼容端点。
模型密钥只交给 AgentTeams/Higress,不进入 RepoPilot 源码、数据库或部署清单。
部署说明:
可复现测试床
测试床包含一个确定性缺陷:合法的 score=0 被 || 1 误判为缺失值。
类型检查通过,CI 只因对应回归用例失败,适合完整演示定位、修复、验证和 PR 证据链。
验证
pnpm typecheck
pnpm test
pnpm lint
pnpm format:check
pnpm build测试覆盖状态机、Webhook 验签、证据哈希、数据库不可变触发器、delivery 并发幂等、 审批版本与一次性消费、HTTP 冲突语义及控制台标签。
安全边界
详细威胁模型与生产加固项见 docs/security.md。
文档导航
文档 | 内容 |
REST、Webhook 和 MCP Schema | |
AgentTeams、Matrix、GitHub、PostgreSQL 和 OTel 方法契约 | |
架构、状态机和部署剖面 | |
权限、审批、凭证和 evidence 完整性 | |
本地、AgentTeams、Webhook 和可观测部署 | |
比赛 Demo 流程与失败分支 | |
初赛简介、评审映射和提交清单 |
当前边界
未配置模型服务时,不能完成真实 AgentTeams 推理;构建、测试、控制面和测试床不受影响。
Runbook 默认使用 PostgreSQL 全文检索;
vector(1536)已为语义召回预留。AgentLoop Recall 是可选能力,没有凭证时自动降级到本地 Runbook。
控制台审批身份当前通过受信反向代理 Header 演示;生产环境必须接入 OIDC/SSO。
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceAn 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.
- Flicense-qualityDmaintenanceMCP server for automated GitHub repository quality management, enabling review, README generation, cleanup, and monitoring.
- AlicenseAqualityBmaintenanceAn MCP server that provides operational tooling over the GitHub API — issue triage, PR review monitoring, repo health audits, and team access reviews.111MIT
- Alicense-qualityBmaintenanceThis MCP server enables automated maintenance and code analysis for Python/pytest repositories in isolated Docker environments. It supports read-only investigations, fix-and-verify tasks, and provides full audit trails with SQLite event history and artifact exports.MIT
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wellkilo/RepoPilot'
If you have feedback or need assistance with the MCP directory API, please join our Discord server