Vercel 扩展
🎥Plug & Play
Watch the demo
本教程介绍如何把 Vercel MCP 服务器 添加为 goose 扩展,以便直接在 goose 里管理 Vercel 项目和部署状态。
信息
运行安装命令需要系统已安装 Node.js,这些命令会用到 npx。
快速安装
- goose Desktop
- goose CLI
npx mcp-remote https://mcp.vercel.com
配置
- goose Desktop
- goose CLI
- Launch the installer
- Click
Yesto confirm the installation - Click the button in the top-left to open the sidebar
- Navigate to the chat
- Run the
configurecommand:
goose configure
- Choose to add a
Remote Extension (Streamable HTTP).
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◆ What type of extension would you like to add?
│ ○ Built-in Extension
│ ○ Command-line Extension
│ ● Remote Extension (Streamable HTTP) (Connect to a remote extension via MCP Streamable HTTP)
└
- Give your extension a name.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streamable HTTP)
│
◆ What would you like to call this extension?
│ Vercel
└
- Enter the Streamable HTTP endpoint URI.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streamable HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◆ What is the Streamable HTTP endpoint URI?
│ https://mcp.vercel.com
└
- Enter the number of seconds goose should wait for actions to complete before timing out. Default is
300seconds.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streamable HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streamable HTTP endpoint URI?
│ https://mcp.vercel.com
│
◆ Please set the timeout for this tool (in secs):
│ 300
└
- Enter a description for this extension.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streamable HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streamable HTTP endpoint URI?
│ https://mcp.vercel.com
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◆ Enter a description for this extension:
│ Access Vercel deployments and manage projects
└
- Choose
Nowhen asked to add custom headers.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streamable HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streamable HTTP endpoint URI?
│ https://mcp.vercel.com
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◇ Enter a description for this extension:
│ Access Vercel deployments and manage projects
│
◆ Would you like to add custom headers?
│ No
│
└ Added Vercel extension
使用示例
goose 提示词
通过 Vercel MCP 服务器列出我的 Vercel 项目,并做一张表,显示我上次部署每个项目的时间,以及其他我该知道的状态细节。
第一次使用 Vercel MCP 服务器时,系统会提示你通过 OAuth 向 Vercel 认证。
goose 输出
我来获取你的 Vercel 项目,并做一张包含部署细节的表。先获取你的团队,以确定用哪个团队列出项目。
> List Teams
> teamId: team_p3hPvXImXmdkbZ36FoqhoyYo
现在获取每个项目的部署信息,查看最近的部署日期和状态:
> projectId, teamId
> projectId, teamId
> projectId, teamId
再获取每个项目的更多细节,以便给出完整的表:
> projectId, teamId
> projectId, teamId
> projectId, teamId
根据你的 Vercel 项目数据,下面是项目状态和部署信息的汇总表:
Vercel 项目概览
| 项目名称 | 框架 | 状态 | 最近部署 | 自定义域名 | GitHub 仓库 | 备注 |
|---|---|---|---|---|---|---|
| project1 | Next.js | 🟡 构建中 | 2025 年 9 月 8 日(今天) | 无 | about-me | 正在构建,最新的项目 |
| project2 | Next.js | ✅ 就绪 | 2025 年 5 月 12 日 | example.com | starter-blog | 站点 2 的备注 |
| project3 | Static | ✅ 就绪 | 2024 年 10 月 25 日 | 无 | sample.com | 站点 3 的备注 |
关键细节与状态摘要
🟡 project1(正在构建)
创建时间:今天(2025 年 9 月 8 日)
状态:正在构建(部署进行中)
最近提交:"first"(2025 年 9 月 8 日)
Node 版本:22.x
问题:这是你最新的项目,部署仍在进行
✅ project2(生产就绪)
创建时间:2024 年 8 月 21 日
状态:生产就绪并已上线
自定义域名:example.com(带 www 重定向)
最近更新:"grammar fix"(2025 年 5 月 12 日)
Node 版本:20.x
活动:最活跃的项目,有 12 次部署
备注:3 月 12 日有一次失败部署,但已成功恢复
✅ project3(生产就绪)
创建时间:2024 年 10 月 25 日
状态:生产就绪
最近更新:"updated public to remove localhost"(2024 年 10 月 25 日)
Node 版本:20.x
活动:一次成功部署
建议
- 关注正在构建的项目:project1 目前还在构建
- 作品集维护:project2 维护良好,使用活跃
- 域名设置:如有需要,考虑给其他项目加上自定义域名
- Node 版本:你混用了 20.x 和 22.x,可以考虑统一
- 所有项目都连到了 GitHub 仓库,并配置了自动部署。