beehiivYou push, switch to the next thing and forget about it. An hour later someone replies to your launch post to say the pricing page still shows the old price.
The build failed at 1:48. Vercel knew straight away. You found out from a stranger.
What the board shows from Vercel
Sign in to Vercel and pick your deployments. The latest ones land as a live list, and you choose what each row says, like the commit that triggered it and whether it built. One project, or every project in a team you allowed.
Vercel’s server also groups runtime errors by the route they hit, which makes a good second widget beside the deploys. Add Sentry’s unresolved issues next to both and the cause and the effect are on one screen.
The board won’t page you when a build fails. It doesn’t send alerts. It keeps your deploys where you already look between tasks, so a failed one gets noticed the next time you glance over.
Where the data comes from
Vercel MCP is Vercel’s official MCP server. The board signs in to it with Vercel’s own sign-in, you grant it the teams you want it to read, and your Vercel permissions still apply. Vercel says the server is available on every plan.
The same server can deploy, change domains and edit settings for agents that ask. The board never runs those tools. It only runs tools that read, so nothing in your Vercel account changes because of it.
Deployments are read again while the board is open, on the schedule you pick. If a read fails, the widget keeps the last good list and says what went wrong and when.
Why a board as well as Vercel
Vercel’s dashboard is where you run your projects. A board is where you see them next to everything else. Today’s commits on one side, the deploys they became in the middle, revenue and errors on the other.
Start from Launch week if a release is coming, or ask your agent to add your deployments to the board you already have.