Vercel Extension
🎥Plug & Play
Watch the demo
This tutorial covers how to add the Vercel MCP Server as a Goose extension to manage your Vercel projects and deployment status directly from Goose.
info
Note that you'll need Node.js installed on your system to run installation commands, which use npx.
TLDR
- Goose Desktop
- Goose CLI
npx mcp-remote https://mcp.vercel.com
Configuration
- Goose Desktop
- Goose CLI
- Launch the installer
- Click
OKto 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 (Streaming 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 (SSE)
│ ● Remote Extension (Streaming HTTP) (Connect to a remote extension via MCP Streaming 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 (Streaming HTTP)
│
◆ What would you like to call this extension?
│ Vercel
└
- Enter the Streaming HTTP endpoint URI.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◆ What is the Streaming 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 (Streaming HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streaming HTTP endpoint URI?
│ https://mcp.vercel.com
│
◆ Please set the timeout for this tool (in secs):
│ 300
└
- Choose to add a description. If you select
No, Goose will skip it.
┌ goose-configure
│
◇ What would you like to configure?
│ Add Extension
│
◇ What type of extension would you like to add?
│ Remote Extension (Streaming HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streaming HTTP endpoint URI?
│ https://mcp.vercel.com
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◆ Would you like to add a description?
│ No
└
- 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 (Streaming HTTP)
│
◇ What would you like to call this extension?
│ Vercel
│
◇ What is the Streaming HTTP endpoint URI?
│ https://mcp.vercel.com
│
◇ Please set the timeout for this tool (in secs):
│ 300
│
◇ Would you like to add a description?
│ No
│
◆ Would you like to add custom headers?
│ No
│
└ Added Vercel extension
Example Usage
Goose Prompt
Get a list of my Vercel projects via the Vercel MCP server, and build me a table showing when I last deployed the project and other details I should know about their status.
The first time you use the Vercel MCP server, you will be prompted to authenticate with Vercel via OAuth.
Goose Output
I'll help you get your Vercel projects and create a table with deployment details. Let me first get your teams to identify which team to use for listing projects.
> List Teams
> teamId: team_p3hPvXImXmdkbZ36FoqhoyYo
Now let me get the deployment information for each project to see the last deployment dates and status:
> projectId, teamId
> projectId, teamId
> projectId, teamId
Now let me get more details about each project to provide a comprehensive table:
> projectId, teamId
> projectId, teamId
> projectId, teamId
Based on the data from your Vercel projects, here's a comprehensive table showing your project status and deployment information:
Vercel Projects Overview
| Project Name | Framework | Status | Last Deployment | Custom Domain | GitHub Repo | Notes |
|---|---|---|---|---|---|---|
| project1 | Next.js | 🟡 Building | Sep 8, 2025 (Today) | None | about-me | Currently building - newest project |
| project2 | Next.js | ✅ Ready | May 12, 2025 | example.com | starter-blog | Notes for site 2 |
| project3 | Static | ✅ Ready | Oct 25, 2024 | None | sample.com | Notes for Site 3 |
Key Details & Status Summary
🟡 project1 (Currently Building)
Created: Today (Sep 8, 2025)
Status: Currently building (deployment in progress)
Last Commit: "first" (Sep 8, 2025)
Node Version: 22.x
Issue: This is your newest project and the deployment is still in progress
✅ project2 (Production Ready)
Created: Aug 21, 2024
Status: Production ready and live
Custom Domain: example.com (with www redirect)
Last Update: "grammar fix" (May 12, 2025)
Node Version: 20.x
Activity: Most active project with 12 deployments
Note: One failed deployment on Mar 12 but recovered successfully
✅ project3 (Production Ready)
Created: Oct 25, 2024
Status: Production ready
Last Update: "updated public to remove localhost" (Oct 25, 2024)
Node Version: 20.x
Activity: Single successful deployment
Recommendations
- Monitor the building project: Check on project1 as it's currently building
- Portfolio maintenance: Your project2 is well-maintained and actively used
- Domain setup: Consider adding a custom domain to your other projects if needed
- Node versions: You have mixed Node versions (20.x and 22.x) - consider standardizing
- All projects are connected to GitHub repositories and have automatic deployments configured.