VibingView × your AI editor

Your workspace.
One conversation away.

Choose your editor, connect through the remote MCP endpoint (or the downloadable local connector), authorize a scoped token, and copy the configuration. Every tool call is permission-checked by your VibingView control plane.

1Choose your editor

Merge this server into your personal MCP configuration, then enable VibingView in Cursor’s MCP settings.

Official Cursor instructions

2Choose how it connects

Your editor talks directly to the VibingView MCP endpoint with your token. Nothing to download.

EndpointStreamable HTTP, JSON responses, bearer authentication. Permissions are checked by the server for every tool call.

3Authorize your account

Or paste an existing access tokenNever paste an infrastructure or provider key here. Tokens stay in this page’s memory, not browser storage.

YOUR CONFIGURATION

Cursor + VibingView

remote http

Merge into ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibingview": {
      "url": "https://vibingview.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_VIBINGVIEW_TOKEN"
      }
    }
  }
}

Copied and downloaded configurations contain your token. Use a private user configuration, never a shared repository. With the CLI, vibingview mcp install merges this for you with owner-only file permissions.

Add your account token to enable copying.

Start a conversation

Save the configuration, reload your editor, review the VibingView tools, then ask:

“List my VibingView workspaces and applications.”

list_workspaces — Your VPS workspaces and their status · read
get_workspace_metrics — Recent CPU, memory, disk and network samples · read
list_applications — Applications and their URLs and status · read
get_application — Health, domains, deployments and variable names (never values) · read
get_build_logs — Build output for a deployment · read
get_runtime_logs — Recent container logs · read
list_databases — Managed databases (no connection strings) · read
list_catalog_apps — One-click application catalog · read
restart_application — Queue a restart (may interrupt traffic) · deploy
rebuild_application — Queue a rebuild and redeploy · deploy
set_environment_variable — Set an encrypted variable; value never echoed · apps:manage
link_database — Link or unlink a workspace database · apps:manage

Mutating tools are queued, not instant, and can interrupt traffic. Review the target and approve each one in your editor. Tools never return environment values or database connection strings.

Manage or revoke tokens

Your workspace.One conversation away.

1Choose your editor

2Choose how it connects

3Authorize your account

Your workspace.
One conversation away.