Cursor vibedeploy begin_deploy
How to: Cursor vibedeploy begin_deploy
Add vibedeploy to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"vibedeploy": {
"url": "https://mcp.vibedeploy.be/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something begin_deploy does. Cursor lists the server's tools on connect and calls begin_deploy itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that vibedeploy's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.