GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http ship https://mcp.letsship.ai/mcp --header 'Authorization: Bearer {token}'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"ship": {
"url": "https://mcp.letsship.ai/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"ship": {
"type": "http",
"url": "https://mcp.letsship.ai/mcp",
"headers": {
"Authorization": "Bearer {token}"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 letsship.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.24.0)于25天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Assign Linear, Jira or GitHub issues to an AI coding agent team. Its coding agents plan and build each change, run code review and tests, and open a pull request in your GitHub repository. With this MCP server, your assistant can file missions, follow them, send instructions and read the proof of each run.
SHIP runs an agentic SDLC as a headless AI software factory. You operate the whole mission from your coding agent or AI assistant. Start it, send instructions, read its code review and test reports, and approve the pull request. A Planner, a Builder, a Reviewer and a Tester each do one stage, and your CI is a gate between them. Each role runs the coding agent and the model that you choose: Claude Code, Codex, OpenCode, Kilo Code or the pi coding agent.
https://mcp.letsship.ai/mcp
The transport is Streamable HTTP. The server is stateless, so a client can reconnect at any time and lose nothing.
OAuth 2.1. A client that supports MCP authorization finds the sign-in automatically. If a request needs a token and has no valid token, the server answers 401 with a WWW-Authenticate header. The header points to https://mcp.letsship.ai/.well-known/oauth-protected-resource/mcp. SHIP supports dynamic client registration and client ID metadata documents, so you do not have to register a client first. You approve the sign-in in the SHIP console.
Personal access token. A client without OAuth sends Authorization: Bearer pat_.... Create a token at https://letsship.ai/settings/tokens. Bind it to one project, so that it can reach only that project.
Claude Code
claude mcp add --transport http ship https://mcp.letsship.ai/mcp
Claude and ChatGPT. Add a custom connector with the URL https://mcp.letsship.ai/mcp. Sign in when the app asks.
Cursor. Use the button above, or add this to .cursor/mcp.json:
{
"mcpServers": { "ship": { "url": "https://mcp.letsship.ai/mcp" } } }
VS Code. Use the buttons above, or add this to .vscode/mcp.json:
{
"servers": { "ship": { "type": "http", "url": "https://mcp.letsship.ai/mcp" } } }
Codex. Add this to ~/.codex/config.toml:
[mcp_servers.ship]
url = "https://mcp.letsship.ai/mcp"
Grok. Open grok.com/connectors. Select New Connector, then Custom. Paste the URL https://mcp.letsship.ai/mcp. Then sign in.
xAI API. Pass the URL as a remote MCP tool, with a token in headers:
{
"type": "mcp", "server_url": "https://mcp.letsship.ai/mcp", "server_label": "ship", "headers": { "Authorization": "Bearer pat_your_token_here" } }
A client that supports only stdio connects through mcp-remote:
{
"mcpServers": { "ship": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.letsship.ai/mcp" ] } } }
With a token. Add the header to any of the HTTP entries above:
{
"mcpServers": { "ship": { "url": "https://mcp.letsship.ai/mcp", "headers": { "Authorization": "Bearer pat_your_token_here" } } } }
Each tool declares readOnlyHint, destructiveHint and openWorldHint. With these hints, your client can run a read-only tool immediately. It can also ask you before it runs a tool that removes or replaces something, or opens a payment page. The scopes of the token decide what each tool can do, and a refusal names the scope that the token does not have.
[!IMPORTANT]
start_mission,create_missionandrun_scheduled_taskstart a mission, and each mission start costs one credit. Messages to an active mission are free.
| Tool | Kind | What it does |
|---|---|---|
start_mission | reaches outside SHIP | Give an issue that is already in your tracker to the agent team. By default, the mission starts at the Planner. With a plan, it starts at the Builder. With an open pull request, it starts at the Reviewer or the Tester |
create_mission | reaches outside SHIP | Create the issue and start the mission in one call, for work that has no issue yet |
send_mission_instruction | reaches outside SHIP | Tell an active mission what to change, or record a note for the agent that runs next |
inspect_mission | reads | The full record of a mission: its stages, verdicts, provenance and session logs |
list_missions | reads | The missions of your projects, with what each mission does now |
get_mission | reads | One mission: its stage, its review and test results, its pull request, its agent runs and the run with the proof. With view: "full", also its events and the outcome of each stage |
pause_mission | writes | Hold a mission before its next stage. The stage that runs now finishes |
resume_mission | reaches outside SHIP | Continue a paused mission. When a checkpoint holds the mission, this approves the result of that stage |
stop_mission | removes | Stop a mission and every agent run of it. The pull request stays open |
approve_mission_ceiling | reaches outside SHIP | Let a mission continue after it stops at its credit limit. The mission then uses more credits |
merge_mission | removes | Merge the pull request of a mission, with the merge method of the repository. On a merge conflict, SHIP starts the Builder to fix the conflict and merges later |
decline_mission | removes | Close the pull request of a mission without a merge |
set_agents_override | replaces | Change the harness, model, prompt or checkpoint of one role for one mission. The override goes on top of ship.yml and does not change the file |
get_agents_override | reads | Read the override that applies to a mission now |
clear_agents_override | removes | Remove the override, so the mission uses the project's configuration again |
set_mission_auto_merge | reaches outside SHIP | Turn auto-merge on or off for one mission. For that mission, the setting replaces the auto-merge of the project |
archive_mission | writes | Hide a mission from the board and from list_missions. Only an owner or an admin can archive a mission |
unarchive_mission | writes | Show an archived mission on the board again |
set_mission_disposition | writes | Record why a mission ended, for example a test or work that another mission replaced, or clear the value. The delivery statistics use this value |
| Tool | Kind | What it does |
|---|---|---|
list_projects | reads | The projects that the token can reach |
get_project | reads | The configuration and connections of one project |
update_project | reaches outside SHIP | Change the name, status, auto-merge, issue code, default sandbox or connections of a project |
list_artifacts | reads | The proof that a run produced, such as test traces and screenshots |
get_artifact | reads | One artifact, with a link to open it |
| Tool | Kind | What it does |
|---|---|---|
list_scheduled_tasks | reads | The missions that a project runs on a schedule |
get_scheduled_task | reads | One scheduled task, with its schedule and prompt |
create_scheduled_task | writes | Add a mission that runs on a schedule |
update_scheduled_task | replaces | Change the schedule or prompt of a scheduled task, or disable it |
run_scheduled_task | reaches outside SHIP | Run a scheduled task now, outside its schedule |
list_scheduled_task_runs | reads | What past runs did, and what they cost |
list_scheduled_task_templates | reads | Templates that you can copy to start a scheduled task |
delete_scheduled_task | removes | Delete a scheduled task and its run history. Missions that the task started continue |
| Tool | Kind | What it does |
|---|---|---|
list_mcp_servers | reads | The servers that the MCP file of a project declares, each with its binding and status |
list_mcp_bindings | reads | Each binding in the projects of your organization, so you can see where each credential is used |
bind_mcp_server | replaces | Choose the agents, transport, approved tools and credential for one server |
unbind_mcp_server | removes | Remove a binding and delete its credential |
refresh_mcp_server_tools | removes | Read the current tool list of the server, so that you can approve tools |
start_mcp_server_oauth | reaches outside SHIP | Get a sign-in link for a remote server, for a person to open in their browser |
set_mcp_config_path | writes | Set a different MCP file for a project, such as .cursor/mcp.json |
| Tool | Kind | What it does |
|---|---|---|
list_agent_runs | reads | Agent runs, live and finished, for one mission, one role or one status |
get_agent_run | reads | The detail and resource use of one run |
get_agent_run_logs | reads | What an agent did inside a run |
watch_agent_run | reads | Wait on one run and follow its events, until the run ends or its mission moves to another stage |
stop_agent_run | removes | Stop the agent in one run before it finishes |
| Tool | Kind | What it does |
|---|---|---|
list_environments | reads | Preview environments that SHIP deployed for open pull requests |
get_environment | reads | One preview environment, with its URL |
destroy_environment | removes | Remove a preview environment early |
| Tool | Kind | What it does |
|---|---|---|
get_billing | reads | The credit balance, the credit limit for each mission and the recent use. Read it before you send work |
list_billing_ledger | reads | Where the credits went, with the newest entry first |
list_credit_offers | reads | The credit packs and the monthly plans, with their prices |
start_credit_checkout | reaches outside SHIP | Open a payment page for a credit pack, a monthly plan or more credits on a plan, and return its URL |
update_team_subscription | removes | Change the monthly plan from the next renewal, or cancel it at the end of the month that you paid for |
request_more_credits | reaches outside SHIP | Ask for more credits. The answer says who has the request |
get_notices | reads | What needs attention in the workspace, such as a tracker that you must connect again |
dismiss_notice | writes | Close a notice that you can close, such as a low balance |
只显示了开头部分;其余内容请在仓库中阅读