Connect Vercel
Vercel is declared in the connector catalogue, but no screen connects a Vercel account. What that means, and the route that does work.
Connect
Vercel hosts and deploys web projects. MaShop declares Vercel in its official connector catalogue, but no screen connects a Vercel account today.
What MaShop can do with Vercel
Nothing executable, through the official connector. The catalogue declares four tools, and this page names them so you are not left guessing: deployment.list, deployment.create, domain.verify and logs.stream. None of the four has an executor. An agent that calls one reads that no executor is wired for that name, and nothing is attempted.
Vercel is also the only one of the six official connectors with no critical tool.
Hosting for your project goes to Netlify instead. Publishing creates two Netlify sites on your own account and builds them from your repository.
What it touches
Nothing. No Vercel token is stored, no Vercel project is created, and no address on Vercel is written by MaShop.
Default permissions
These are the states the tools modal shows if a Vercel card is proposed in your chat. They are a setting, not a live power.
| Tool | Level | Default state |
|---|---|---|
| deployment.list | Read only | Allow |
| logs.stream | Read only | Allow |
| deployment.create | Write and edit | Ask |
| domain.verify | Write and edit | Ask |
One trap worth naming: domain.verify exists on both Vercel and Resend, and a permission is stored under the bare tool name. Setting it on one sets it on the other.
Connect it
There is no Vercel connection screen. The Deployment tab of Project settings offers three services: GitHub, Netlify and Supabase.
If the assistant proposes a Vercel card in the chat, its Connect button opens the publishing flow of your project, not a Vercel authorization. Its Documentation button opens the Vercel documentation in a new tab.
One route does work. Vercel publishes its own MCP server, and it sits in the MaShop directory of thirty services.
- Open the avatar menu, Account settings, Connectors tab.
- Keep the toggle on Your connectors.
- Search for Vercel in the directory and click Add on its card.
- Approve on Vercel, and you land back in MaShop.
That gives your agents the tools Vercel exposes on its own server, and those ones really run. A call is relayed to Vercel and executed. They are not the four declared above.
Expect to sign each of those calls. No screen sets a permission for a remote tool, so the guard falls through to your signature, unless the agent is set to autonomous.
Check that it works
There is nothing to check for the official connector, since nothing is connected. If you added Vercel as an MCP server, its card appears in your connector list with its host and a switch. The return message reads: Service connected. Your agents can now use it.
Known gap: no screen lists the tools of a connected MCP server, so the card shows the host without a tool count.
Limits
- Four declared tools, zero executable.
- No account authorization path for Vercel in the workspace.
- Deployment targets Netlify. Nothing publishes to Vercel.
- The Official badge on a chat card comes from the model that proposed it, not from a verification.
When it breaks
- Connect opens the publishing flow. That is the current behaviour for every official connector card, not a fault of your account.
- An agent says no executor is wired. The tool is declared but not implemented. Nothing was attempted, so nothing was changed on your side.
- A permission you set on Resend changed on Vercel. The shared tool name is the cause.
Remove the connection
There is nothing to remove for the official connector, because no token is stored.
If you plugged in the Vercel MCP server, turn its switch off in Account settings, Connectors, Your connectors. The line moves to revoked and every stored token is erased. The authorization stays valid at Vercel until you revoke it there.