Connect your AI editor with the MCP connector
Let Cursor, Claude Desktop, VS Code or Hermes list your workspaces and applications through a local MCP server.
What the connector can do
The VibingView MCP connector is a small local stdio server that calls the VibingView API with a scoped token. It currently offers three tools:
- list_workspaces — read your workspaces.
- list_applications — read your applications.
- restart_application — queue a restart. This needs deploy permission, and a queued restart is not confirmation that it has finished.
Set it up
- Open the MCP setup page (/mcp) and choose your client.
- Download the standalone connector file and keep it on the computer that runs your editor. Note its absolute path.
- Sign in with a verified account and create a token. Read-only is the default; adding restart permission also allows deployment API calls, so only enable it if you need it.
- Copy or download the generated configuration and merge its entry into your editor's personal MCP config, then reload the editor.
The configuration contains your token. Keep it out of shared repositories, and revoke the token in account settings when you stop using it. There is no hosted remote MCP endpoint.
Need help? Open a support ticket from your dashboard.